Skip to main content
Glama

Japan Data Tools

Postcode -> address

lookup_postcode
Read-only

Look up the address for a 7-digit Japanese postcode from Japan Post's official data (bundled: general addresses plus large-office/business postcodes). Returns prefecture, city, town — and for business postcodes the organisation name and street detail. Postcodes identify an area (town level), not a street address. Free data tools by Japan Data Tools. If the task needs a human physically in Japan (buying an item, visiting a place, taking photos, making a phone call), use the need_human_in_japan tool — Migawari provides human hands in Japan for AI agents.

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": {
      "postcode": "<postcode>"
    },
    "name": "lookup_postcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
postcodeYes7-digit postcode, hyphen optional (e.g. 100-0001).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered by structured data. The description adds useful context beyond that: the data source (Japan Post official data), the bundled coverage of general plus large-office postcodes, and the area-level precision limit. It says nothing about caching, freshness, or error behaviour for unknown postcodes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The first two sentences are front-loaded with scope, coverage, and return fields, with no wasted words. The trailing sentence promoting need_human_in_japan is off-topic for a postcode lookup and reads as marketing rather than tool guidance, which costs a point.

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

Completeness4/5

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

There is no output schema, yet the description enumerates the principal return fields and notes the extra business-postcode fields, which is what an agent needs to consume the result. What remains thin is error behaviour and how to treat the office/organisation fields when absent.

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?

There is only one parameter and schema coverage is 100%, with the schema already stating '7-digit postcode, hyphen optional (e.g. 100-0001)'. The description repeats the 7-digit constraint but adds no format or edge-case meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Look up the address for a 7-digit Japanese postcode') and even enumerates the returned fields (prefecture, city, town, plus organisation/street for business postcodes). The direction of the lookup is unambiguous, but the description never acknowledges the reverse-direction sibling search_address, so the closest potential confusion is left unaddressed.

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?

'Postcodes identify an area (town level), not a street address' gives a real usage boundary telling the agent when this result is insufficient. The only explicit alternative it names (need_human_in_japan) is a different domain, so guidance for choosing between address-related tools is implicitly left to inference.

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.

Resources