Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

turkey_crypto_exchange_prices

Read-onlyIdempotent

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 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/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and freshness profile is largely covered structurally. The only added context is the word "real-time," which is thin and unelaborated (no refresh cadence, no source exchanges, no coverage of pairs). It does not contradict the annotations, but it adds very little beyond them.

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 brevity is achieved by vacuity rather than efficiency: the entire sentence after the colon simply repeats the name. No sentence here earns its place, and nothing is front-loaded beyond the title.

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?

There is no output schema, so the description must convey what comes back — exchange names, trading pairs, bid/ask or last price, timestamps, currency — and it conveys none of it. For a data-feed tool with open-world access, the definition is too thin for an agent to predict results or decide relevance.

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?

With a single parameter and 100% schema description coverage, the schema already documents maxResults fully (type, default 10, meaning). The description adds no meaning about what a "record" contains or how maxResults affects the response, so the baseline of 3 applies.

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 is essentially a tautology: it restates the tool name and title ("Turkey Crypto Exchange Prices") and wraps it in vendor-ish filler ("Real-time structured data extraction feed"). It never states a verb + resource like "fetch current TRY-denominated crypto prices from Turkish exchanges," nor does it separate this tool from near-neighbours such as 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 Guidelines1/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 when-not-to-use, and no named alternative. With a dense cluster of crypto/FX siblings in the catalog, the absence of any routing guidance leaves the agent no basis for choosing this tool over them.

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