Skip to main content
Glama

Trova una località

resolve_location
Read-onlyIdempotent

Resolve a town name to coordinates before geographic searches. Multiple matches require disambiguation. Results include source attribution and public DalVivo URLs.

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": {
      "q": "<q>"
    },
    "name": "resolve_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes

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 is covered. The description adds useful behavior — ambiguous names require disambiguation and results carry source attribution and public DalVivo URLs — but never says what a disambiguation outcome looks like (candidate list vs. error), which is the one thing an agent most needs to handle this case.

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?

Three short sentences, front-loaded with purpose then disambiguation behavior then result content, with no filler. Sizing is appropriate for a one-parameter resolution tool.

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?

With no output schema, the description does a reasonable job stating what results contain (source attribution, public URLs). The gap is the disambiguation flow — whether the tool returns multiple candidates, requires a retry, or errors — which matters for an agent deciding whether one call suffices.

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 0%, so the description must carry the burden; it does identify that the single parameter is a town name, which is the essential semantics. However, it omits format guidance (e.g., partial names, 'City, Country', handling of the 2–120 character constraint), leaving some ambiguity about what inputs are acceptable.

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 gives a specific verb (resolve), a specific input resource (a town name) and the concrete output (coordinates), plus its role relative to sibling search tools ('before geographic searches'). An agent can distinguish it from search_places/get_place without opening any schema.

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?

'Resolve a town name to coordinates before geographic searches' establishes clear sequencing guidance relative to the geographic search siblings. It stops short of naming an explicit alternative or exclusion, but the when-to-use context is unambiguous.

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