Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

turkey_gold_prices

Read-onlyIdempotent

Turkey Gold Prices - Gram, Quarter, Ons + 35 Banks: Real-time structured data extraction feed for Turkey Gold Prices - Gram, Quarter, Ons + 35 Banks.

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_gold_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 by structured fields. The description contributes only the word 'Real-time' (a freshness claim) plus 'structured data extraction feed', which conveys little. It omits the data source, update cadence, historical depth, and what '35 Banks' contributes, all of which matter for an open-world scraping feed.

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 half of the text is a verbatim repeat of the tool title, so the second clause earns no place. There is no front-loaded statement of action; the agent reads a label twice before learning anything. Trimming the duplication would leave a leaner but still under-specified line.

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?

No output schema exists, so the description must convey what the feed returns (fields, granularity, units, bank coverage) and it does not. For an open-world real-time price feed with an ambiguous '35 Banks' qualifier, an agent cannot tell whether it gets a single aggregate quote or a per-bank table. The single simple parameter keeps the gap from being fatal, but the definition is thin for the tool's scope.

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) and schema description coverage is 100%, so the schema fully documents it. The description adds no meaning about result ordering, default size, or whether more results cost more. Baseline 3 applies when the schema does 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 is essentially the title restated twice: 'Turkey Gold Prices - Gram, Quarter, Ons + 35 Banks' followed by a near-verbatim echo. It never supplies a verb+resource statement such as 'fetch current Turkish gold prices per gram, quarter, and ons from 35 banks,' so the agent must infer that this retrieves prices. The '35 Banks' fragment is left unexplained, and no sibling is distinguished (e.g., versus turkey_crypto_exchange_prices).

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 preconditions, and no mention of any alternative tool. 'Real-time' hints at a freshness advantage but does not tell the agent under what circumstances to prefer this feed over other Turkey price tools. Usage is only implied by the topic word 'prices'.

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