subsidy_watch_get
Get a subsidy program detail plus full event timeline. Returns firstSeenAt and ledgerVerified.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| programId | Yes |
Japan Public Ledgers MCP
Schema Changelog
Changes observed during successful MCP inspections.
- First observed
TDQS
B3.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, but the description hints at read-only operation and specifies returned fields. Lacks disclosure on permissions or side effects.
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 front-loaded sentences with no fluff.
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?
Covers basic purpose and return fields, but missing parameter description and output structure detail; adequate for a simple get but incomplete given no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Parameter programId is not described at all, despite 0% schema coverage; description fails to explain its purpose or format.
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?
Clearly states it retrieves a subsidy program detail and full event timeline, distinguishing it from sibling tools like search, changes, or verify.
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 guidance on when to use this tool versus alternatives like subsidy_watch_timeline or subsidy_watch_search.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.