Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_czk

Paid. USD/CZK exchange rate and inverse, latest ECB reference fix. $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/forex-rates/usd-czk.

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

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 behavioral burden and does well: it discloses the pricing model ($0.002 USDC), the accepted payment chains (Base or Solana), the absence of auth requirements, and a billing guarantee that failed calls are not charged. Remaining gaps are latency, freshness/cadence of the ECB fix, and the shape of the paid response, but the economically critical facts are all present.

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?

Front-loads the most decision-relevant token ("Paid.") and then the resource, followed by cost, payment rails, and billing policy in short clauses. Every sentence earns its place except the raw endpoint URL, which is informational rather than actionable for most agents.

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, annotation-free, output-schema-free paid lookup, the description covers what an agent needs before calling: cost, payment method, auth requirements, failure billing, data source, and directionality (rate and inverse). Only response format and update cadence are unstated, which are minor for a single-value endpoint.

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 there is nothing for the description to disambiguate beyond confirming the pair is fixed rather than caller-specified. That baseline is met and the description correctly implies no inputs are needed.

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 and scope: the USD/CZK rate plus its inverse, sourced from the latest ECB reference fix. An agent knows exactly what data comes back. However, it never distinguishes itself from the large family of fx siblings (e.g. buy_fx_czk, buy_fx_usd_eur, buy_fx_usd), so the pair-selection logic is left to the name alone.

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?

It implies the usage context by stating the tool is paid, that no account or API key is needed, and that failed calls are free, which tells an agent this is a pay-per-call endpoint rather than a free lookup. It gives no explicit guidance on when to choose this pair tool over a sibling such as buy_fx_czk or the broader buy_fx_usd, and no mention of rate limits or when the ECB fix refreshes.

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