Skip to main content
Glama

Evendo Places

Resolve a place name

resolve_place
Read-only

Find the Evendo ID of a country, region, city or neighbourhood by name. Always call this first: other tools take place IDs, not names. Names can be ambiguous (several 'Soho's), so check address_city / country_code in the results and pick the right one. If you don't know what kind of place it is, omit place_type.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPlace name, spelled correctly, e.g. "Prague", "Scotland", "Soho".
limitNo
place_typeNoCities for cities, Neighbourhoods for districts, CountryRegions for regions like Scotland or Bavaria (if none found, try Regions, then omit place_type), Destinations for destination areas, Country for countries.
country_codeNoISO 3166-1 alpha-2, e.g. "GB", to disambiguate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real substance beyond them: results contain address_city and country_code fields, results can be multiple matches for ambiguous names like 'Soho', and the agent is expected to pick among them. It doesn't describe result ordering or what fields exist beyond those two, which keeps it short of a 5.

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?

Four short sentences, front-loaded with the purpose and the must-call-first rule, followed by the disambiguation hint and a conditional parameter note. No sentence is redundant and nothing important is buried.

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 carries the burden of explaining what comes back, and it does name the key result fields used for disambiguation. It stops short of describing the full result shape or the effect of limit, but for a read-only lookup this is close to complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75% and the place_type enum is already well documented in the schema, but the description still adds a decision rule the schema lacks ('If you don't know what kind of place it is, omit place_type'). The one uncovered parameter, limit, is never mentioned in the description, leaving that gap unaddressed.

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?

States a specific verb and resource: 'Find the Evendo ID of a country, region, city or neighbourhood by name.' It also implicitly separates itself from the sibling tools by declaring that other tools take place IDs rather than names, so an agent knows this is the entry point.

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

Usage Guidelines5/5

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

Explicit ordering instruction: 'Always call this first: other tools take place IDs, not names.' It also gives disambiguation procedure (check address_city / country_code in the results) and a fallback rule for place_type, which covers the main decision points an agent faces when calling it.

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.