Skip to main content
Glama

Kripto para fiyatları (TL)

finans_get_crypto_prices

Fetch live cryptocurrency prices in Turkish lira from BtcTurk or Paribu exchanges, including BTC, ETH and USDT pairs, so you can check current TRY values for crypto assets.

Instructions

Live cryptocurrency prices in TRY from Turkish exchanges BtcTurk or Paribu (kripto, bitcoin, ethereum, USDT). Default pairs BTC_TRY, ETH_TRY, USDT_TRY.

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_crypto_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
borsaNoBorsabtcturk
paritelerNoPariteler, ör. ["BTC","ETH_TRY","AVAXTRY"]. Boşsa BTC, ETH, USDT.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose genuine behavioral context the schema lacks: the data originates from Turkish exchanges, is denominated in TRY, and is described as 'live'. It stops short of stating return shape, freshness/latency, or what happens when an exchange feed fails or an unknown pair is requested.

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 short sentences, front-loaded with the core capability and followed by the default scope. No filler, no repetition of the title.

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

Completeness4/5

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

For a zero-required-parameter read tool with full schema coverage and no output schema, this is nearly sufficient: source, currency and defaults are all stated. The only real gap is the absence of any note on what the response contains or how failures surface.

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 baseline 3 applies. The description reinforces the default pair behaviour ('Default pairs BTC_TRY, ETH_TRY, USDT_TRY') and names the two exchange values, but adds no syntax guidance for the pariteler array beyond what the schema already shows.

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 ('Live cryptocurrency prices in TRY') and pins the data source to two named Turkish exchanges. An agent can immediately separate this from finans_get_gold_prices or finans_get_exchange_rates by the asset class and TRY denomination.

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 implied by the topic and the listed default pairs, so an agent knows this is the crypto-price tool. However there is no explicit when-to-use or when-not-to-use statement, and no guidance on which exchange to choose when the answer might differ between BtcTurk and Paribu.

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