Skip to main content
Glama

Get town

get_town
Read-onlyIdempotent

Overview of one Boken Japan town (municipality): names EN/JA, coordinates, access (nearest station, car needed), official links, address and phone of the town office, listing counts by type, section pages, sample listings and stays with checked booking links.

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": {
      "prefecture": "<prefecture>",
      "town": "<town>"
    },
    "name": "get_town"
  }
}

Input Schema

NameRequiredDescriptionDefault
townYesTown slug or name, e.g. "hakuba"
prefectureYesPrefecture slug or name, e.g. "nagano"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, and non-open-world behavior. The description adds useful context about what the response contains: names, coordinates, access details, official links, office contact data, listing counts, section pages, and sample listings. It does not mention behavior for missing towns, but the annotations carry the safety profile.

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 description is a single front-loaded sentence with no filler, starting with the core purpose. The long enumeration of returned fields is dense but earns its place because there is no output schema.

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?

With no output schema, the description does well by enumerating the main categories of returned information. It is complete enough for a read-only lookup tool whose annotations already cover safety, though it could briefly mention not-found behavior.

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 description coverage is 100%, so the schema already explains that town and prefecture accept slugs or names with examples. The description adds no parameter-specific syntax or constraints beyond what the schema provides, making baseline 3 appropriate.

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?

The description clearly identifies the resource and scope: an overview of one Boken Japan town/municipality. It distinguishes itself from list_towns by specifying a single town, though it does not explicitly name or contrast sibling tools.

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 the phrase 'Overview of one ... town,' which suggests this is the lookup tool for a specific municipality. However, it gives no explicit when-to-use guidance, prerequisites, or alternatives such as using list_towns to discover town slugs.

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