Time-ordered events only for an ordinance (the differentiator: when it appeared / was amended / was repealed). Includes firstSeenAt and ledgerVerified.
| Name | Required | Description | Default |
|---|---|---|---|
| itemId | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the full burden. It discloses that events are time-ordered and include firstSeenAt and ledgerVerified, but omits details like ordering direction (ascending/descending), pagination, limits, or error behavior. This is adequate but not comprehensive.
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?
Two sentences, no wasted words. The description efficiently communicates the tool's purpose, differentiator, and key fields. It is front-loaded with the core functionality.
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?
The tool is simple but the description leaves gaps: it does not specify output ordering, event structure beyond two fields, or limits. Without an output schema, this omission hampers an agent's ability to interpret results correctly.
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?
The only parameter (itemId) is required but not described in the schema (0% coverage). The description implies it's the ordinance ID, but does not explicitly explain its format or how to obtain it. A more explicit description would add value.
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 tool returns time-ordered events for an ordinance, specifically when it appeared, was amended, or repealed. It distinguishes itself from other ordinance tools by emphasizing 'the differentiator' and mentions included fields, making the purpose unambiguous.
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 this is the timeline tool for ordinances but does not explicitly state when to use it versus other ordinance tools like get, search, recent_changes, or verify_ledger. There is no guidance on prerequisites or when not to use it.
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.