Skip to main content
Glama
Sign In

GMPSignal Real-Time Intelligence MCP

by io.github.xpayrcom
OverviewDiscussionsAdmin

turkey_domestic_flight_prices

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 structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Real-time" and "extraction feed" suggest live scraped data, but the description says nothing about freshness guarantees, rate limits, pagination, failure modes, or whether an API key is needed. It also says nothing about what the returned items look like.

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

Conciseness3/5

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

It is a single short sentence that is front-loaded, so there is no bloat. However, half of it is a redundant repeat of the tool name, which is wasted space rather than earned concision.

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?

For a data-extraction tool with no output schema, the description should at least sketch the returned fields (route, airline, date, price, currency). Instead it names no fields, no coverage of airports or dates, and no pagination or freshness behavior, leaving the agent unable to predict results.

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) with 100% schema description coverage, so the schema already explains it fully. The description adds no meaning beyond that, but baseline 3 applies when 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 almost verbatim ("Turkey Domestic Flight Prices" twice) without a verb or resource statement. "Real-time structured data extraction feed" hints at a price data feed, but an agent gains no more than it could guess from the name itself. No differentiation from siblings like turkey_bus_routes_prices or turkey_car_rental_prices_city_airport_index.

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 guidance on when to use this tool, when not to, or which sibling handles adjacent transport-price queries. An agent must infer from the name alone that this covers domestic flights rather than buses, ferries, or car rentals.

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

All GMPSignal Real-Time Intelligence MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources