mcp-server

get_city_info

Get detailed information about a specific city by its geonameid

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": {
      "geonameid": "<geonameid>"
    },
    "name": "get_city_info"
  }
}

Input Schema

Name	Required	Description	Default
`geonameid`	Yes	The unique geonames identifier for the city

Schema Changelog

Changes observed during successful MCP inspections.

First observedJan 31, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says 'Get', implying a read operation, but it does not describe return format, error behavior, rate limits, or what 'detailed information' includes. There is no added context beyond the basic action.

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 a single sentence, front-loaded with the action, and contains no unnecessary words. It is as concise as possible while conveying the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description provides enough to understand the basic operation but lacks contextual richness. It does not explain what 'detailed information' means, how to interpret the response, or how this tool fits with the sibling. It is functional but not comprehensive.

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?

The input schema description for 'geonameid' is clear and covers the parameter fully (schema_description_coverage=100%). The tool description mentions 'geonameid' but adds no meaningful semantics beyond that. Per the baseline rule for high schema coverage, a score of 3 is appropriate.

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 tool's purpose: 'Get detailed information about a specific city by its geonameid'. It uses a specific verb ('Get'), identifies the resource ('detailed information about a specific city'), and includes the key parameter ('geonameid'). This distinguishes it from the sibling tool find_random_fivepm_city, which focuses on random selection.

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?

The description provides no guidance on when to use this tool versus the sibling find_random_fivepm_city. It does not mention prerequisites (e.g., having a valid geonameid) or exclusions. The context is minimal, leaving the agent to infer usage without explicit direction.

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

All mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?