Skip to main content
Glama

Buscar un destino

find_destination
Read-onlyIdempotent

Look up a city or airport the way wiz-trip.com's search box does: returns matching cities with their IATA code, country and airports. Use it when a city name is ambiguous (several Santiagos) before searching.

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

Input Schema

NameRequiredDescriptionDefault
queryYesCity or airport name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely new context: it mirrors the site's search-box matching and reveals the result shape (city, IATA code, country, airports). It omits matching rules (fuzzy vs prefix) and what an empty result means, which keeps it below 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?

Two sentences, no filler. The core behavior and return fields come first, then the disambiguation use case, so the most decision-relevant information is front-loaded.

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

Completeness5/5

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

A one-parameter lookup with no output schema, and the description still tells the agent what each result contains (city, IATA code, country, airports). Nothing needed to call it correctly is missing; the remaining unknowns are minor matching-behavior details.

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% for the single 'query' parameter, so the baseline is 3. The description adds meaning beyond 'City or airport name' by framing the input as something that can match multiple cities and by tying it to ambiguity resolution, telling the agent to expect a name-shaped, not ID-shaped, input.

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 ('Look up a city or airport') plus what comes back: matching cities with IATA code, country and airports. This cleanly separates it from siblings like search_flights and search_hotels, which are inventory searches rather than name resolution.

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?

Gives a concrete trigger ('when a city name is ambiguous (several Santiagos)') and an ordering cue ('before searching'), which implicitly routes to the search_* siblings. It stops short of naming those alternatives explicitly or stating when not to bother 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.

Resources