Skip to main content
Glama

List towns

list_towns
Read-onlyIdempotent

Without prefecture: the 47 prefectures with town and listing counts. With prefecture: every town in it with names, page URL and listing counts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_towns"
  }
}

Input Schema

NameRequiredDescriptionDefault
prefectureNoPrefecture slug or name, e.g. "akita"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restatement. The description does add useful payload detail — listing counts, town names and page URLs — which helps an agent decide whether the call answers its question, but it says nothing about result size, ordering, or pagination for large prefectures.

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?

Two dense clauses, no filler, and the no-argument case is front-loaded before the parameterized case. Every phrase carries information about either scope or returned fields.

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 single optional parameter with no output schema, the description covers both invocation modes and the fields returned, including the reassuring word 'every' that implies no hidden paging. The remaining gap is minor: no statement of result ordering or limits for a prefecture with many towns.

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% and the schema already gives an example slug ('akita'), so the baseline is 3. The description contributes meaning beyond the schema by explaining what omitting versus supplying the parameter does to the result shape, which is genuine added semantics but not deep parameter detail.

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 names a specific verb and resource (list towns) and splits the behavior into two clearly stated modes: no prefecture yields the 47 prefectures with town and listing counts, while a prefecture yields every town with names, page URL and listing counts. That is concrete enough to distinguish it from get_town or search_places, though it never explicitly contrasts itself with those siblings.

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 conditional structure 'Without prefecture... With prefecture...' effectively tells the agent which mode it gets and therefore when to pass the optional parameter. It stops short of naming an alternative tool or stating exclusions (e.g., when to prefer search_places), so it is clear context rather than full routing guidance.

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