Skip to main content
Glama

SouthPow crypto & market data

buy_fx_pln

Paid. Forex rates from PLN to 29 other currencies, 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/pln.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 well: it discloses cost ($0.01 USDC), accepted payment chains (Base or Solana), that no auth is required, and that failed calls are not charged. It stops short of describing the response payload or rate timestamp granularity, but the key operational behaviors are covered.

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?

Everything is front-loaded in short, scannable fragments, and each line adds a distinct fact (purpose, source, price, chain, auth, failure policy, URL). The telegraphic style ('Paid.') and the raw URL are slightly rough, but nothing is padded.

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 cost, payment rails, auth, data source, and failure billing, which is what an agent needs to call it safely. The only real gap is return-shape detail (what fields the rates payload contains), which is a minor omission at this complexity.

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 and the description correctly describes it as a fixed PLN-base endpoint with no configuration, matching the empty schema. Baseline is 4 for a no-parameter tool; no meaningful semantics are missing.

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 ('Forex rates from PLN') plus the scope ('to 29 other currencies'), which is exactly what distinguishes it from the pair-style siblings like buy_fx_eur_pln or buy_fx_usd_pln. It also names the data source ('latest ECB reference fix'), so an agent knows both the direction of the quote and the provenance.

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 description makes clear this is a paid call with no account or API key needed and that failures are free, which helps an agent decide to invoke it. However, it never explicitly routes against the many alternative FX siblings (e.g. 'for EUR-based rates use buy_fx_eur') and states no when-not conditions. Usage is implied by the base currency rather than stated as guidance.

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