tos_watch_timeline
Time-ordered events only for a ToS document (the differentiator: when it appeared and each revision since). Includes firstSeenAt and ledgerVerified.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| itemId | Yes |
Japan Public Ledgers MCP
TDQS
B3.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It only mentions return fields (firstSeenAt, ledgerVerified) but does not explain auth needs, rate limits, error handling, or whether the operation is read-only. Minimal transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with key purpose, no redundant information. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description is too sparse. It does not specify output format, pagination, errors, or prerequisites. For a tool with a single parameter, it lacks sufficient detail for an agent to use correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%. The description mentions 'a ToS document' but does not explicitly define the itemId parameter or provide format/example. It adds little meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it provides time-ordered events for a ToS document, including firstSeenAt and ledgerVerified. This distinguishes it from sibling tools like tos_watch_get (current state) and tos_watch_recent_changes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for historical timeline by saying 'when it appeared and each revision since', but it does not explicitly state when to use this tool over alternatives like tos_watch_get or tos_watch_recent_changes. No when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3/5.0
Disambiguation3/5
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.
Naming Consistency4/5
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.
Tool Count1/5
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.
Completeness4/5
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.