Skip to main content
Glama
Sign In
nankai-trough-mcp

nankai-trough-mcp

by mrslbt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Geocode a Japanese Address

geocode_address
Read-onlyIdempotent

Convert a Japanese address to latitude/longitude coordinates and parse prefecture/municipality using the official GSI geocoder. Get precise coordinates for hazard map lookups.

Instructions

Convert a Japanese address to coordinates (lat/lon) and parse the prefecture/municipality, via the official GSI geocoder. Utility used by official_hazard_maps; call it directly when you only need coordinates.

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": {
      "address": "<address>"
    },
    "name": "geocode_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesJapanese address to geocode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds useful context about the official GSI geocoder and its relationship to official_hazard_maps, providing extra behavioral framing without contradicting annotations.

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 two sentences, front-loaded with the core action, and provides sibling context without unnecessary fluff. Every clause contributes to understanding the tool's purpose and usage.

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?

The tool is simple with a single parameter, no output schema, and meaningful annotations. The description covers the main purpose, the external geocoder, and the scenario for direct use. It does not mention output format details, but for a simple geocoding tool this is acceptable.

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% as the 'address' parameter includes its own description. The tool description repeats the parameter's purpose without adding extra semantic detail like formatting or examples. However, it does clarify that the address must be Japanese, which is slightly beyond the schema.

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 specific verb 'Convert' with the resource 'a Japanese address' and the output (coordinates and prefecture/municipality). It also distinguishes from siblings by noting it's a utility used by official_hazard_maps, making its role unambiguous.

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

Usage Guidelines5/5

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

The description explicitly says 'call it directly when you only need coordinates', which indicates when to use this tool versus relying on official_hazard_maps. It also implies that official_hazard_maps is the higher-level alternative.

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

Deploy Server

Other Tools