Skip to main content
Glama

Altın ve değerli metal fiyatları

finans_get_gold_prices

Retrieve Turkish free-market gold, silver, platinum, and palladium prices in TRY, with optional codes to filter specific metals or request FX rates.

Instructions

Turkish free-market gold prices (altın fiyatları: gram, çeyrek, yarım, tam, Cumhuriyet, 22/18/14 ayar), silver, platinum and palladium in TRY. Optionally any code from the feed (e.g. USD, EUR for free-market 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": "finans_get_gold_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
kodlarNoYalnız bu kodlar, ör. ["GRA","CEYREKALTIN","USD"]. Boşsa tüm değerli metaller.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does reveal that this reads from a live feed and that arbitrary feed codes (including FX) are accepted, but it says nothing about whether returned prices are buy/sell/mid, what units or timestamps accompany them, or how stale the data may be.

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

Conciseness5/5

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

Two sentences, front-loaded with the resource and currency, with the karat list packed into a single parenthetical. Nothing is redundant and the optional-parameter note comes last.

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

Completeness3/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 is the only place return-value shape could be described, and it omits it entirely (no buy/sell convention, no field names, no timestamp). For a simple single-optional-parameter quote tool this is adequate but leaves a real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so a 3 is the baseline; the description earns above that by clarifying that the single kodlar parameter accepts ANY code from the feed, not just metals — e.g. USD/EUR for FX. That is genuine added meaning the schema alone does not convey.

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?

States a specific verb and resource: free-market gold prices in TRY, enumerating the karat/coin types (gram, çeyrek, yarım, tam, Cumhuriyet, 22/18/14 ayar) plus silver, platinum and palladium. That level of specificity lets an agent distinguish it from finans_get_exchange_rates or finans_get_crypto_prices without opening the schema.

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

Usage Guidelines3/5

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

Usage is only implied — an agent infers 'call this when you need gold/precious-metal prices'. There is no explicit when-to-use vs. the exchange-rates sibling, and the line about passing USD/EUR 'for free-market FX' actively blurs the boundary with finans_get_exchange_rates without saying which to prefer.

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