Register an agent and get a unique identity ID + issuer-signed badge. agent_name/metadata are self-reported and unverified.
| Name | Required | Description | Default |
|---|---|---|---|
| metadata | No | ||
| agentName | Yes | ||
| publicKey | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that agent_name and metadata are self-reported and unverified, and indicates outputs. However, it does not mention whether the operation is destructive, requires authentication, or has side effects, leaving significant behavioral gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the main purpose, and contains no extraneous information. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (3 params, nested objects, no output schema), the description provides the core purpose and a caveat but lacks parameter details for publicKey, output format, and behavioral specifics. It is adequate but not fully comprehensive for an AI agent to use without additional context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It adds meaning for agentName and metadata (self-reported) but omits any mention of publicKey. The description partially covers 2 of 3 parameters, leaving a key parameter undocumented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'register' and the resource 'agent', and specifies the outputs: 'unique identity ID + issuer-signed badge'. The caveat about self-reporting distinguishes it from verification tools like agent_identity_lookup.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use (for registering a new agent) but does not explicitly state when not to use or mention alternatives. The caveat about self-reporting provides some guidance but not sufficient for clear differentiation from sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes, especially the ledger-watch groups with domain prefixes. However, there are near-duplicate utilities such as content_authenticity_domain_reputation and domain_intel_reputation, and fx_tax_convert overlaps with price_oracle_fx_rate/convert. The sheer number of tools also increases the chance of selecting the wrong one, though descriptions are generally clear.
The naming is largely consistent with a <domain>_<action> or <domain>_<watch>_<action> pattern, and all names use snake_case. Minor deviations include standalone names like entity_search, kyb_report, verify_receipt, and the confusing singular/plural pair of sanction_watch_* and sanctions_screen_*. Overall, the pattern is predictable.
With 172 tools, this server is far beyond the typical well-scoped range. It bundles dozens of unrelated utility domains (weather, carbon, CVE, geo, etc.) alongside the Japan public-ledger watches, making it unwieldy for an agent to navigate. This extreme count is a major coherence problem.
For the core Japan public-ledger domain, coverage is excellent: each ledger has search, get, timeline, recent_changes, and verify_ledger, plus cross-ledger entity_search and temporal_query. The unrelated utility areas are also fairly complete for their own purposes, but the server's scope is so broad that some utilities are duplicated (e.g., multiple currency converters). Overall, no critical dead ends in the main domain.