Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP

tcmb_exchange_rates_official_turkish_central_bank_fx

Read-onlyIdempotent

TCMB Exchange Rates - Official Turkish Central Bank FX: Real-time structured data extraction feed for TCMB Exchange Rates - Official Turkish Central Bank FX.

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": "tcmb_exchange_rates_official_turkish_central_bank_fx"
  }
}

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 contributes only the vague claim of 'real-time' data, without saying how fresh the rates are, whether a date range is supported, or what happens when TCMB publishes no rate for a day/holiday. With annotations carrying the load this is not a contradiction, but the added value is minimal.

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 single sentence is short but circular, repeating the same title twice with only a generic filler phrase in between. It is under-specified rather than concise — the words present earn nothing.

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-feed tool with no output schema, the description should convey what records come back (currency pairs, buy/sell rates, date fields) and the time scope. None of that is present, so an agent cannot judge whether results match a request for a specific currency or date.

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 a complete schema description, so the schema fully documents it. The description adds no meaning beyond that, which lands at the baseline of 3 under high schema coverage.

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 a near-tautology: it restates the tool name twice ('TCMB Exchange Rates - Official Turkish Central Bank FX ... for TCMB Exchange Rates - Official Turkish Central Bank FX') without adding a verb+resource statement of its own. All the clarity comes from the name itself; the phrase 'real-time structured data extraction feed' is generic filler that could describe any scraping tool. It does not distinguish this from siblings like global_central_bank_macro_rates_inflation_tracker.

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 mention of alternatives, and no exclusions (e.g., whether this covers only current rates or historical dates, or how it differs from the global macro rates sibling). Usage is only implied by the topic 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.