Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_try

Paid. USD/TRY exchange rate and inverse, latest ECB reference fix. $0.005 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/forex-rates/usd-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": "buy_fx_usd_try"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses the cost ($0.005 USDC), accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It stops short of stating rate freshness/caching behavior or the response shape, which are the remaining behavioral unknowns.

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?

Roughly five short sentences, front-loaded with the paid status and the resource, with each snippet adding a distinct fact (cost, delivery, auth, refund policy, endpoint). The telegraphic fragment style is efficient but slightly terse; no sentence is wasted.

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-parameter paid lookup with no output schema, the description supplies the essentials: what data, what source, what cost, where payment settles, and refund behavior. The gaps are the response field structure and rate freshness, which an agent would want before spending money.

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?

The schema has zero parameters, so the baseline is 4. The description reinforces this by stating no account or API key is needed, confirming the tool is callable with no input, though it does not explain how payment is authenticated if no credential is supplied.

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

Purpose4/5

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

The description names a specific resource and scope: the USD/TRY rate plus its inverse, sourced from the latest ECB reference fix. That is far more specific than the name alone. It does not explicitly contrast itself with the many near-identical siblings (buy_fx_try, buy_fx_eur_try, buy_fx_usd_eur), leaving disambiguation to the pair encoded in the tool name.

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 pair name and the 'Paid' framing, and the cost/no-account details help an agent decide it is callable. However, there is no explicit when-to-use or when-not-to-use guidance against the alternatives, which matters given ~40 sibling fx tools with identical shape.

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