subsidy_watch_timeline
Time-ordered events only for a program (the differentiator: when it appeared, changed, closed). Includes firstSeenAt and ledgerVerified.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| programId | Yes |
mcp-revenue-empire — Japan public-data ledgers
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description bears full burden. Does not disclose read-only/destructive nature, authentication needs, or data freshness. Only mentions included fields (firstSeenAt, ledgerVerified) but no behavioral traits beyond that.
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 concise sentences with no redundancy, front-loading key information and efficiently using parentheticals.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a one-parameter tool with no output schema, but lacks details on expected return format, pagination, or error handling. Could be more complete given no annotations.
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?
The only parameter 'programId' lacks any description in schema or text. The description adds no meaning (e.g., format, example, or how to obtain it), leaving agents without context despite low schema coverage.
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 the tool provides 'time-ordered events only for a program' and specifies the differentiator ('when it appeared, changed, closed'), distinguishing it from sibling watch_timeline tools and other subsidy watch tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives like subsidy_watch_get or subsidy_watch_recent_changes. The 'differentiator' hint is present but not actionable without comparison to siblings.
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.1/5.0
Disambiguation4/5
Most tools are clearly distinguished by domain prefixes (e.g., bid_watch, grant_watch) and specific action verbs. However, the high number of similarly structured watch tools could still cause confusion, though descriptions clarify exact purposes.
Naming Consistency5/5
Every tool follows a consistent `domain_subdomain_action` pattern with underscores, e.g., `agent_audit_query`, `bid_watch_search`. Even long names like `commerce_catalog_agent_readiness_score` adhere to this structure.
Tool Count2/5
With 147 tools, the server is far too broad, covering weather, carbon estimates, domain intel, and more—well beyond its stated 'Japan public-data ledgers' scope. This sheer volume overwhelms agents and dilutes focus.
Completeness3/5
The server offers many read-only tools for Japanese public data (bids, grants, licenses, etc.), but lacks create/update/delete operations for those domains. Additionally, numerous unrelated tools (e.g., carbon estimates, weather) feel tacked on, leaving gaps in core coverage.