Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

turkey_domestic_flight_prices

Read-onlyIdempotent

Turkey Domestic Flight Prices: Real-time structured data extraction feed for Turkey Domestic Flight 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_domestic_flight_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.2/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. The description's only addition is 'real-time', a mild freshness hint; it says nothing about data sources, update cadence, or failure behavior beyond that.

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 circular: the resource name is repeated twice and 'real-time structured data extraction feed' is filler rather than front-loaded substance. Brevity here comes from under-specification, not from disciplined editing.

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

Completeness2/5

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

With no output schema and an arbitrary open-world data feed, the description should at least sketch what a returned record is (route, airline, price, date) or what the feed covers. It leaves an agent unable to predict results before calling.

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 parameter (maxResults) with 100% schema description coverage, so the schema already explains it. The description adds no further semantics, which is acceptable at this coverage level, hence the baseline 3.

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 almost verbatim ('Turkey Domestic Flight Prices: ... feed for Turkey Domestic Flight Prices') and adds only the generic phrase 'real-time structured data extraction feed'. An agent learns the domain but nothing about what a record contains or how the data is scoped.

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 statement of when another sibling (e.g. ferry schedules or bus routes) would be the better choice, and no prerequisites or exclusions. The domain implied by the name is the only cue.

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