Skip to main content
Glama

obilet_search_locations

Search obilet.com cities, towns, and airports by name to get location IDs for bus journey or flight summary queries.

Instructions

Search obilet.com locations (cities, towns, airports) by name. query: e.g. "Ankara", "İstanbul", "İzmir". kind: "bus" (default, int ids) or "flight" (string ids like "250_0"). Returns id, name, display name and city id per match. Use the id in obilet_search_bus_journeys (bus) or obilet_flight_summary (flight).

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

Input Schema

NameRequiredDescriptionDefault
kindNobus
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden. It does disclose a real quirk — bus ids are ints while flight ids are strings like "250_0" — and names the returned fields, but it says nothing about matching behavior (partial vs exact, Turkish character handling), result limits, or authentication needs.

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?

The purpose is front-loaded in the first sentence, followed by compact per-parameter notes and a closing routing hint. There is no filler; every clause, including the example ids, conveys usable information.

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?

An output schema exists, so the brief return-field mention is a bonus rather than a requirement, and both parameters are addressed despite zero schema coverage against a 2-parameter tool. The only shortfall for a search tool is the absence of guidance on match quality and ambiguity handling.

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 description coverage is 0%, so the description must compensate, and it largely does: query is illustrated with concrete city examples, and kind is documented with both allowed values, the default, and the associated id type per mode. It still omits match semantics and whether an empty or ambiguous query is an error.

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 description opens with a specific verb and resource plus scope: search obilet.com locations (cities, towns, airports) by name. That is far more than the tool name alone and tells an agent exactly what kind of entity is resolved here versus the journey/detail siblings.

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?

It explicitly routes the agent forward: use the returned id in obilet_search_bus_journeys for bus or obilet_flight_summary for flight, and the kind parameter selects which. There is no explicit when-not-to-use or note about calling this without a downstream lookup, but the workflow context is clear.

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