Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_try

Paid. EUR/TRY exchange rate and inverse, latest ECB reference fix. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/forex-rates/eur-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_eur_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 supplied, the description carries the full burden and does meaningful work: it discloses that the call is paid, the exact price and payment chains, that no auth is needed, that failures are not charged, and that the underlying data is the ECB reference fix. It does not state update cadence ('latest' is vague) or the response payload shape.

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?

Telegraphic and front-loaded ('Paid.' first, then what you get, then how to pay). Every fragment carries information. The raw endpoint URL is of marginal use to an agent and slightly clutters an otherwise dense definition.

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, no-output-schema tool, the description covers the essentials an agent needs to decide and pay: what data, its provenance, the price, accepted chains, and that failures are free. It stops short of describing the returned fields or rate timestamp, which is the only remaining 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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies no arguments are needed and instead spends its words on cost and data source, which is the right allocation for a parameterless call.

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?

Names a specific resource (EUR/TRY exchange rate), states it also returns the inverse, and identifies the data source as the latest ECB reference fix. An agent can distinguish it from the many other buy_fx_* siblings by the explicit currency pair, though it never names an alternative it is not.

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?

The payment terms ('$0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged') tell the agent the cost and prerequisite conditions, which implicitly gates usage. However, there is no explicit when-to-use statement or routing to a cheaper/alternative tool such as a free rate source or the sibling buy_fx_try/buy_fx_eur.

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