Skip to main content
Glama

SouthPow crypto & market data

buy_fx_czk

Paid. Forex rates from CZK to 29 other currencies, 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/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_czk"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses paid pricing ($0.002 USDC), accepted payment rails (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits rate limits, caching/freshness behavior, and the response shape.

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?

Roughly four short sentences, each carrying distinct information: what the data is, the source, the price and rails, the failure policy, and the endpoint. The scoping information is front-loaded and there is no filler.

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 endpoint with no output schema, the description covers cost, payment method, data provenance, and billing on failure. The remaining gap is the return payload: with no output schema present, the description should say what fields or currencies the response contains.

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 and the baseline of 4 applies. The stated scope (CZK to 29 currencies) effectively defines the fixed query.

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?

States a concrete verb and resource: forex rates FROM CZK to 29 other currencies, with the specific data source (latest ECB reference fix). The CZK base is explicit, which distinguishes it from buy_fx_eur_czk and buy_fx_usd_czk (inverse pairs). It does not, however, reference any sibling by name, so direction disambiguation is left to the agent's reading of 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 only implied: an agent can infer it should call this when it needs CZK-based FX rates. There is no explicit guidance about when to prefer the inverse pair (buy_fx_eur_czk) or the USD-based equivalent, and no note on whether the rate is a single snapshot or a historical series.

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