Skip to main content
Glama

biletall_search_locations

Search biletall.com locations by city or town name to retrieve matching slugs, names, and URLs for use in bus and flight route queries.

Instructions

Search biletall.com locations (cities, towns) by name. query: e.g. "Ankara", "İstanbul", "İzmir", "Bodrum". Searches the platform location inventory offline (1,726 slugs from the site's sitemap; major cities carry correct Turkish spelling). Returns slug, name and the location's biletall.com URL per match. Use the slug (or the city name) in the bus/flight route tools.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the search is offline against 1,726 slugs sourced from the sitemap, that major cities carry correct Turkish spelling, and what each match returns (slug, name, URL). It does not mention limits on result size or behavior when nothing matches, which keeps it from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, followed by parameter example and then the operational detail and workflow hint. The parenthetical about the sitemap is slightly verbose but genuinely informative, so little is wasted.

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?

Output schema exists, so return values need not be explained (though slug/name/URL are helpfully summarized). For a two-parameter lookup tool, the definition is nearly complete; only the undocumented 'limit' parameter is a real gap.

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 0%, so the description must compensate. It does well for 'query' (examples like "Ankara", "İstanbul", "Bodrum" and the hint that city names work), but the 'limit' parameter is never mentioned in either schema or description.

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: search biletall.com locations (cities, towns) by name. This is clearly distinguishable from the sibling route/price tools, and the description even notes what the tool is used for downstream.

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?

Explicitly says to use the resulting slug (or the city name) in the bus/flight route tools, which gives a clear when-to-use context and workflow position. It lacks an explicit when-not-to-use or named alternative for direct lookups, but the guidance is strong.

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