Tool/Agent Registry

Problem

If the coordinator's tool palette and the list of available specialist agents are hardcoded into prompts, every new capability requires a redeploy and selection logic gets duplicated everywhere. Keeping tools and agents in separate registries leads to two parallel selection paths with diverging metadata: cost, latency, capability, and quality may be tracked one way for tools and a different way for agents, so the coordinator cannot meaningfully rank candidates across the two.

Solution

Provide a registry that exposes a queryable catalogue of (1) tools — typed inputs/outputs, cost, latency, allowed contexts — and (2) agents — capability descriptions, supported tasks, model and provider, price. The agent queries the registry per task, ranks candidates by suitability, and dispatches. The registry can be backed by a coordinator agent with a curated knowledge base, a blockchain smart contract, or extended into a marketplace; metadata stays small (descriptions and attributes), not full schemas, to keep the registry lightweight.

When to use

• Many tools and/or agents are available and selection is non-trivial.
• A central catalogue (internal or external marketplace) can be maintained.
• Selection metadata (cost, quality, context window) actually changes the pick.