arp-jarvis-tool-registry 0.1.0b2

Tool Registry service for ARP runtimes (tool discovery, schemas, invocation).

Tool Registry

This repo will contain the Tool Registry service: a standalone tool provider for ARP runtimes.

Current phase: MVP implementation (stdlib HTTP server).

Design docs

• docs/intro.md
• docs/design/overview.md

Install

From PyPI (once published):

pipx install arp-jarvis-tool-registry

Pre-release (e.g. 0.1.0a1):

pipx install --pip-args="--pre" arp-jarvis-tool-registry

Or in a virtualenv:

pip install arp-jarvis-tool-registry

Run locally

Create a virtualenv, then install and run the service:

python3 -m venv .venv
source .venv/bin/activate

pip install -e .

arp-jarvis-tool-registry

Env vars:

• TOOL_REGISTRY_HOST (default 127.0.0.1)
• TOOL_REGISTRY_PORT (default 8000)
• TOOL_REGISTRY_DOMAINS (default core)

Endpoints:

• GET /v1alpha1/health
• GET /v1alpha1/version
• GET /v1alpha1/tools
• GET /v1alpha1/tools/{tool_id}
• POST /v1alpha1/tool-invocations (body: {"invocation_id":"...","tool_id":"...","args":{...}})

More docs:

• docs/intro.md
• docs/adding_tools.md

Run tests

From the repo root:

python3 -m unittest discover -v

Or (if you have pytest installed):

pytest -q

MVP capabilities + known gaps

Capabilities:

• Tool discovery (GET /v1alpha1/tools) and detail (GET /v1alpha1/tools/{tool_id}).
• Validated invocation (POST /v1alpha1/tool-invocations) with normalized ToolInvocationResult/ErrorEnvelope.
• Simple in-repo “domain modules” pattern for adding tools.

Known gaps:

• No auth, rate limiting, or multi-tenant policy layer yet.
• Stdlib HTTP server only (FastAPI/ASGI swap is a future improvement).
• No MCP aggregation implementation in this MVP.