Skip to main content
Glama

Get town

get_town
Read-only

One town: guide link, official site, coordinates, its verified places, and upcoming reviewed events.

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

Input Schema

NameRequiredDescriptionDefault
townYesTown name or slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that returned places are 'verified' and events 'reviewed', hinting at curation, but says nothing about behavior for an unknown town, partial matches, or result limits.

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?

A single front-loaded sentence with no filler; every listed item is substantive. The telegraphic fragment style ('guide link', 'official site') is efficient but slightly opaque about what those values actually are.

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 one parameter, no output schema, and annotations covering safety, the description does the main job of telling the agent what comes back. Only edge-case behavior (town not found, empty events) is unaddressed, which is minor for a simple read tool.

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 single 'town' parameter is documented as 'Town name or slug'. The description adds no further meaning about accepted formats, case sensitivity, or slug resolution, so the schema does all the work and the baseline of 3 applies.

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 the resource precisely ('One town') and enumerates its payload: guide link, official site, coordinates, verified places, and upcoming reviewed events. That makes it distinguishable from siblings like get_place or search_places, though the retrieval verb itself is only implied by the noun phrase rather than stated.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus get_place, search_places, or events, nor any note about prerequisites such as resolving a name to a slug first. Usage is only inferable from the tool name and the listed payload.

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