Skip to main content
Glama
Sign In

GMPSignal Real-Time Intelligence MCP

by io.github.xpayrcom
OverviewDiscussionsAdmin

turkey_crypto_exchange_prices

Turkey Crypto Exchange Prices: Real-time structured data extraction feed for Turkey Crypto Exchange 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_crypto_exchange_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about which exchanges are scraped, freshness guarantees behind 'real-time', authentication or rate limits, or whether data is cached. 'Real-time structured data extraction feed' is a marketing phrase rather than behavioral disclosure, so the agent cannot anticipate the data's shape or reliability.

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?

The sentence is short but wastes most of its length repeating the tool name verbatim. It is not under-informative because of length but because the single sentence is circular, so brevity earns no credit here.

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

Completeness1/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 annotations, no output schema, and no examples, the description should specify what records are returned, their fields, and the data source. None of that is present, leaving an agent unable to predict the response at all.

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 only one optional parameter, maxResults, and schema description coverage is 100%, so the schema already explains it as 'Maximum number of structured items to extract.' The description adds nothing further, but the baseline of 3 applies when the schema fully documents the parameter.

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 only restates the tool name: 'Turkey Crypto Exchange Prices: Real-time structured data extraction feed for Turkey Crypto Exchange Prices.' It adds no verb-plus-resource specificity beyond the title and does not distinguish this from crypto-related siblings like crypto_orderbook_arbitrage_scanner or tcmb_exchange_rates_official_turkish_central_bank_fx.

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 alternative to pick. A user wanting Turkish crypto prices versus an orderbook arbitrage scan versus official FX rates gets no help choosing, so usage is left entirely to inference.

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