Skip to main content
Glama
Sign In

Adónde

by com.getadonde
OverviewDiscussionsAdmin

Search places

search_places
Read-onlyIdempotent

Looks up cities, regions and countries by name as someone types, e.g. Lisb or Ireland. Returns up to 6 candidates, each with name, country, kind (city, region or country), coordinates and a label such as Lisbon, Portugal. Reads only; creates nothing. The trip form's destination box calls it; call it yourself only to check a spelling before start_trip. Use get_city_guide to learn about a city, suggest_route to choose cities in a country.

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": "search_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesWhat was typed, at least 2 characters.
limitNoHow many candidates, up to 6 (default 6).
country_codeNoOnly places in this country, ISO two-letter code, e.g. US; used for domestic trips.

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, idempotentHint and destructiveHint=false, so 'reads only; creates nothing' is largely redundant. The description does earn credit beyond them by disclosing the result shape (up to 6 candidates with name, country, kind, coordinates, label) since there is no output schema.

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, each carrying distinct information: purpose, return shape, safety, and routing. The typeahead behavior and the start_trip condition are front-loaded where an agent will read them.

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 3-param read-only lookup with no output schema, the description covers purpose, result fields, cap size and alternatives — enough to call correctly. It stops short of mentioning behavior on zero matches or how ambiguous queries are resolved, which is a minor gap.

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 100%, so the baseline is 3, and the description adds genuine semantics: partial/prefix input is expected ('as someone types, e.g. Lisb') and results are capped at 6, which clarifies how `q` and `limit` behave in practice rather than just restating them.

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 ('looks up cities, regions and countries by name') plus the typeahead/as-you-type semantic and a concrete example ('Lisb or Ireland'). It clearly separates itself from siblings get_city_guide and suggest_route, so an agent can pick it 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 Guidelines5/5

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

Explicit routing: 'call it yourself only to check a spelling before start_trip', plus named alternatives for the adjacent needs ('use get_city_guide to learn about a city, suggest_route to choose cities in a country'). It also says the destination box ordinarily calls it, which explains why an agent rarely needs it directly.

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

All Adónde toolsInspect
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