Agent tool registry¶
The Agent Tool Registry lists the current public tools, their interfaces and
access requirements. Generated by argus.core.tool_registry, it is the
machine-readable source of truth. Use this guide to discover and interpret tools;
query the registry for the current inventory.
Primary discovery paths¶
| Interface | Discovery entry point | Role |
|---|---|---|
| CLI + Skill | argus tool-registry |
Primary local Agent interface; emits JSON only. |
| REST | GET /v1/tool-registry |
HTTPS and batch transport; no sign-in needed for discovery. |
Every registry tool declares exactly three bindings: CLI, MCP and REST. A missing binding is a release error unless the tool is explicitly marked internal.
The public MCP endpoint, https://mcp.argusfa.com/mcp, lists and calls only
the 20 consumer tools, with OAuth. Those tools are an
MCP-only facade over registry tools and are not registry entries.
agent_tool_registry and the other registry tools are neither listed nor
callable there: a call answers Unknown tool. Discover registry tools through
argus tool-registry or GET /v1/tool-registry, and call them through the CLI
or REST. The machine MCP endpoint that serves their MCP bindings is internal,
and the public edge answers 404 for it.
Each entry has a discovery_group: core, personal, advanced or
diagnostics. Advanced and diagnostics tools need explicit signed grants.
The registry includes the bounded stream family. stream_subscribe remains finite by
duration and event count; the CLI binding is a cursor/poll operation, while MCP
and REST return the same bounded structured event window.
Registry contract¶
Each entry declares:
- stable tool id and semantic version;
- versioned input schema, canonical envelope version, and typed payload family;
- coded capability, four-field time semantics, and provider coverage metadata;
- structured title and description metadata for discovery;
- input and output schema identifiers (
release/schema-catalog.v1.jsoncontains the normalized kernel schemas;/openapi.jsonand MCPlist_toolsexpose native executable request schemas); - the actual wire output format, or typed
DataPackagepayload name; - CLI command, MCP tool name, and REST path;
- binding-specific
parameter_aliases,parameter_encodings, and credential location; - required scopes,
default_oauth_access, allowed purposes, and authentication requirements; - data-source, license, freshness, and point-in-time capabilities;
- lifecycle state, replacement id, and removal version when deprecated;
- prohibited capabilities and structured safe alternatives.
Tool responses never contain generated natural-language analysis, investment advice, portfolio recommendations, strategy decisions, or order instructions. Discovery descriptions are metadata; invocation output is structured data only.
Compatibility invariant¶
Given the same normalized request and authorized identity, CLI + Skill, MCP, and REST must return semantically equivalent payloads, evidence, time semantics, quality flags, license restrictions, errors, and audit records. Adapter-specific envelopes may differ only where the transport protocol requires it.
python scripts/generate_interfaces.py emits the MCP bindings, REST models,
Skill contract, and generated documentation from this registry. The CLI
binding table is built in memory by the same script (cli_bindings()) and is
not written to a file.
python scripts/generate_interfaces.py --check is a CI gate. Documentation
must link to the registry instead of maintaining a second tool table; generated
artifacts are the only allowed rendered inventory.