Skip to main content
Glama
Sign In
turkey-data-mcp

turkey-data-mcp

by bodyegypt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Turkey Gold & Silver Prices

get_gold_prices

Retrieve current gold and silver prices in Turkey (TRY). Covers gram gold, Turkish coins, and silver with buy/sell rates, daily change, weight, and purity.

Instructions

Get current gold and silver prices in Turkey, quoted in Turkish lira (TRY). Source: Harem Altın, cross-checked with TCMB; refreshed every 5 minutes. Returns buy/sell prices, daily change (% and amount), weight and purity for: gram gold (14k/18k/22k/24k), Turkish gold coins (çeyrek/quarter, yarım/half, tam/full, cumhuriyet/republic, ata) and silver per gram. Use the optional 'category' filter to narrow results; omit it for everything. Use this for questions like 'gram altın ne kadar?', 'quarter gold coin price in Turkey', or 'how much is 24k gold in Istanbul today?'.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoFilter by category: 'gram' = gold per gram (14k–24k), 'coin' = Turkish gold coins (çeyrek, yarım, tam, cumhuriyet, ata), 'silver' = silver per gram, 'all' (default) = everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses data source (Harem Altın, cross-checked with TCMB), refresh interval (every 5 minutes), and return details (buy/sell prices, daily change, weight, purity). This is substantive, though it doesn't mention potential limitations or error cases.

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

Conciseness4/5

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

The description is five sentences, but each sentence adds practical value: purpose, source/refresh, return contents, parameter behavior, and example queries. It's slightly longer than minimal but well-organized and front-loaded with the core purpose.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with no output schema, the description fully covers what the tool returns, how to use it, and its data freshness/source. It is complete and self-sufficient.

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?

Schema description coverage is 100%, so the schema already explains the 'category' enum values. The description adds a minor usage hint about omitting it for everything, but doesn't add new semantic meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool gets current gold and silver prices in Turkey, quoted in TRY, with specific detail on weight/purity categories. This distinguishes it from sibling tools like get_exchange_rates and get_fuel_prices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit example queries ('gram altın ne kadar?') and explains the optional category filter's behavior ('omit it for everything'). This gives clear when-to-use guidance, though it doesn't explicitly mention alternatives, the usage context is unambiguous.

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

Deploy Server

Other Tools