tako-mcp

get_postal_areas

Retrieve prefecture, city, and area information by Japanese postcode.

Instructions

Look up area information by Japanese postcode. Returns prefecture, city, and area. No authentication required.

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": "get_postal_areas"
  }
}

Input Schema

Name	Required	Description	Default
`postcode`	Yes	Japanese postcode, e.g. 916-0045

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Mar 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It correctly identifies this as a read-only operation by stating 'look up' and explicitly mentions 'No authentication required'. It also describes the return values. However, it doesn't disclose potential limitations like data freshness or rate limits, which is acceptable for a simple lookup.

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?

The description is extremely concise: two sentences that cover the purpose, return values, and authentication requirement. Every word is meaningful, and the structure is front-loaded with the key action and outcome.

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?

For a simple one-parameter lookup tool without an output schema, the description provides all necessary context: what it does, what it returns, and that it requires no authentication. It is fully complete for an AI agent to correctly select and invoke the tool.

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

Parameters4/5

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

The input schema already provides 100% coverage for the 'postcode' parameter with an example. The description adds value by specifying the output (prefecture, city, area), which the schema does not provide. This helps the agent understand what the tool returns.

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 verb 'look up', the resource 'area information by Japanese postcode', and specifies the returned fields (prefecture, city, area). It is easily distinguishable from sibling tools (get_account_info, get_electricity_consumption) which serve entirely different domains.

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?

The usage context is implicitly clear due to the tool's specific domain (postal areas) versus siblings (account info, electricity consumption). It mentions 'No authentication required', indicating public availability. No explicit when-not-to-use guidance is needed given the narrow scope.

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

Deploy Server