Skip to main content
Glama
Sign In

official.tokyo.jp

by io.github.dror-jp
OverviewDiscussionsAdmin

Get a procedure

get_procedure
Read-onlyIdempotent

Get one procedure by ID: steps in order, deadline, where to go, human-verified official government links (lg.jp/go.jp) and the last_verified date. Use list_procedures first to find the ID.

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": {
      "id": "<id>"
    },
    "name": "get_procedure"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStable slug, e.g. 'resident-registration'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuinely new context: results contain human-verified official government links (lg.jp/go.jp) and a last_verified date, which conveys data provenance and freshness that no annotation provides.

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, both earning their place: the first front-loads what the tool returns, the second front-loads the prerequisite. No filler or redundant restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema present, the description carries the burden of describing return content and does so (steps, deadline, location, links, last_verified), and the single required parameter is fully documented in the schema. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100% and the schema itself documents the 'stable slug, e.g. resident-registration' semantics. The description only restates 'by ID', which is slightly looser terminology than the schema's slug wording and adds no format or validity detail beyond it. Baseline 3 applies.

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?

States a specific verb and resource ('Get one procedure by ID') and enumerates what comes back: ordered steps, deadline, location, verified official links, and last_verified date. This makes it clearly distinct from list_procedures, which is named as the discovery path.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent to run list_procedures first to obtain the ID, which is a concrete prerequisite. It stops short of stating when not to use this tool (e.g., for bulk retrieval or name-based lookups), so it is strong but not exhaustive.

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

All official.tokyo.jp toolsInspect
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