Skip to main content
Glama

Find place codes

mb_find_place
Read-onlyIdempotent

Convert a city, airport, station, or hotel name into the correct search code for flight, train, bus, taxi, or hotel queries.

Instructions

Turn a city, airport, station or hotel name into the code a search takes.

flight: airports (Iranian IATA codes; Tehran is THR; prefer to XXXALL for domestic routes) and cities (any country; XXXALL = all its airports). train: station ids. bus / taxi: 8-digit city ids (11320000 = Tehran, all terminals). hotel: city and hotel slugs.

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>",
      "mode": "<mode>"
    },
    "name": "mb_find_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesWhich search the code is for.
limitNoMax places per list.
queryYesPlace name in Persian or English, or a code, e.g. 'مشهد', 'tehran' or 'IST'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • changedInput schema / properties / mode / description
      Previous value: -"Which search the code is for; each mode uses its own ids."New value: +"Which search the code is for."
    • removedInput schema / title
      Removed value: -"mb_find_placeArguments"
  2. Changed4 schema fields changedv0.3.0
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / mode / title
      Removed value: -"Mode"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "mb_find_placeDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds useful domain behavior: which identifier format each mode consumes (IATA codes, station ids, 8-digit city ids, slugs) and the XXXALL wildcard semantics. It does not explain response shape beyond 'list'.

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?

The intent is front-loaded in one sentence, followed by a compact per-mode reference block with no filler. The telegraphic style ('prefer to XXXALL', 'hotel: city and hotel slugs') is dense but readable; a little more connective wording would help without adding length.

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?

There is no output schema, but the description signals that results come back as per-mode lists ('Max places per list') and which code formats to expect, which is close to complete for a lookup tool. The actual fields of each returned place (name, code, disambiguating region) are never described.

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; the description goes further by explaining what each `mode` value actually yields in terms of code format, and by showing concrete code examples (THR, 11320000 = Tehran, all terminals). That is meaning beyond the enum labels.

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 opening sentence gives a specific verb and resource: convert a place name into the code a search expects. It also names the accepted input classes (city, airport, station, hotel), which cleanly separates this resolver from all the sibling search tools.

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?

The phrase 'the code a search takes' makes the sequence clear (look up here before calling a search tool), and it offers a real preference rule: use XXXALL for domestic routes and for all airports of a city. It stops short of naming a specific sibling search tool or stating what to do when a lookup returns nothing.

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