Skip to main content
Glama

Find a Japanese postcode by address

search_address
Read-onlyIdempotent

Find postcodes by part of a Japanese address or an office name, e.g. 大阪市北区梅田.

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": {
      "text": "<text>"
    },
    "name": "search_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesPart of the address in Japanese

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds the useful behavioral detail that partial address fragments and office names are both valid inputs. It says nothing about match multiplicity or whether zero results is a normal outcome.

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?

A single sentence that front-loads the verb and resource, then the input scope, then a concrete example. No filler, no restatement of the title, nothing that could be cut.

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?

For a one-parameter read-only lookup with rich annotations and no output schema, the description is nearly sufficient. The remaining minor gap is that it never indicates whether the result is a single postcode or multiple candidates, which matters for an agent deciding how to present or retry.

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?

Schema coverage is 100% for the single 'text' parameter, so the baseline is 3. The description earns an extra point by expanding the parameter's meaning beyond the schema wording: the field accepts not just part of an address but also an office name, illustrated with a real Japanese example.

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?

States a specific verb and resource ('Find postcodes by part of a Japanese address') plus the accepted input type and a concrete Japanese example. It does not distinguish itself from the sibling lookup_postcode, so an agent cannot tell which direction of lookup each tool serves from the description alone.

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?

Usage is implied by 'by part of a Japanese address or an office name' and the sample string, making it clear this is a forward search on partial text. There is no explicit when-to-use versus when-not guidance and no sibling alternative is named, so routing against lookup_postcode is 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