Japan Public Ledgers MCP

license_watch_recent_changes

Recent appearance / revoked / suspended events across all license ledgers since the given ISO8601 timestamp. Each item includes firstSeenAt and ledgerVerified.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "since": "<since>"
    },
    "name": "license_watch_recent_changes"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`since`	Yes
`registry`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 17, 2026

TDQS

A3.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description must cover behavioral traits. It describes output fields (firstSeenAt, ledgerVerified) but omits side effects, authentication, rate limits, or whether it is read-only. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with key information. No unnecessary words. Efficiently conveys purpose and key point about output fields.

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?

With 3 parameters (one required), no output schema, and no annotations, the description covers the main functionality and time filter. However, it lacks explanation for 'registry' and 'limit', and could better differentiate from sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. The description clarifies the 'since' parameter as ISO8601 timestamp, but does not explain 'limit' or 'registry'. Adds meaning to one of three parameters.

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 lists recent events (appearance/revoked/suspended) across all license ledgers, with a temporal filter. It distinguishes from siblings like license_watch_get and license_watch_search by focusing on recent changes and the scope 'across all license ledgers'.

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 recent changes since a timestamp, but lacks explicit when-to-use vs alternatives. No direct comparison to sibling tools like license_watch_timeline or other watch recent_changes tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Japan Public Ledgers MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?