Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

turkey_bus_routes_prices

Read-onlyIdempotent

Turkey Bus Routes & Prices: Real-time structured data extraction feed for Turkey Bus Routes & Prices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "turkey_bus_routes_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description's only added behavioral claim is 'real-time', which is not elaborated (refresh cadence, whether prices are scraped live or cached, coverage of operators/cities). It says nothing about the shape of results, pagination, or failure modes for an open-world scraper-style feed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

It is short, but almost every word is wasted: the tool name appears twice, separated by a colon, plus a generic 'structured data extraction feed' phrase. No sentence conveys actionable information, and there is no front-loaded statement of what a caller gets back.

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

Completeness3/5

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

With one optional parameter, full schema coverage, and no output schema, the structural gaps are small — but this is an open-world data feed whose value depends entirely on knowing what fields come back and what geography/timeframe is covered, and the description supplies none of that. For a simple read-only feed it is minimally serviceable rather than complete. No contradiction with annotations, which mark it as a safe idempotent read.

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?

There is a single optional parameter (maxResults) and the schema documents it at 100% coverage with a default of 10, so the description is not required to compensate. It adds no meaning beyond the schema — no note on sensible page sizes or record caps. Baseline 3 applies because the schema does all the work.

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

Purpose2/5

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

The description restates the tool name and title almost verbatim ('Turkey Bus Routes & Prices: ... feed for Turkey Bus Routes & Prices'), adding only the vague filler 'real-time structured data extraction feed'. It never says what a record actually is — a route schedule, a fare, an operator list, or a city pair — so an agent cannot predict the returned content. The subject domain (Turkish intercity bus pricing) is the only differentiator from siblings, and that comes from the name, not the description.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or exclusions. Nearby siblings such as turkey_domestic_flight_prices and turkey_greek_islands_ferry_schedules cover adjacent transport questions, yet the description never indicates which mode of query belongs here. The agent must infer everything from the tool name.

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