Skip to main content
Glama

Airsockfly

Suggest places

suggest_places
Read-onlyIdempotent

Resolve a city, airport or region name to place suggestions with IATA codes that the search tools accept.

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

Input Schema

NameRequiredDescriptionDefault
queryYesText to look up, for example a city or airport name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds return-value context beyond annotations (results carry IATA codes usable by search tools), but says nothing about multiple/zero matches, ranking, or whether results are cached.

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?

One sentence, front-loaded with the verb and the input, ending with the payoff (codes the search tools accept). No filler or redundant restatement of the title.

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 simple one-parameter lookup with full schema coverage and rich annotations, the description covers input, purpose and the usefulness of the output. The only meaningful omissions are ambiguity behavior (multiple suggestions) and the shape of a suggestion beyond its IATA code.

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 coverage is 100% for the single 'query' parameter, so the baseline is 3. The description only marginally extends the schema by adding 'region' to the accepted input types, while the schema's own maxLength and example already cover the rest.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ('Resolve') plus the resource ('a city, airport or region name') and states the output ('place suggestions with IATA codes'). It implicitly separates itself from the search_* siblings by framing itself as the step that produces codes those tools accept, though it never names a sibling.

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

Usage Guidelines3/5

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

The phrase 'that the search tools accept' implies this is a prerequisite discovery step before search_flights/search_hotels, which is useful implied guidance. However, there is no explicit when-to-use statement, no exclusion versus list_destinations/get_destination, and no advice on what to do when the query is ambiguous.

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