Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_pln

Paid. USD/PLN 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/usd-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_usd_pln"
  }
}

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, the description carries the full burden and does a solid job: it discloses that the call is paid ($0.01 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged. It does not cover latency, rate limits, or cache/update cadence beyond 'latest ECB reference fix', which are relevant for a paid endpoint.

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?

Front-loaded with 'Paid.' then the resource, then cost/rails, then failure policy, then the endpoint URL. Five short clauses, no filler, and every sentence conveys operational information the agent needs.

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?

There is no output schema, so the description must convey the return shape; it does say both the rate and its inverse are returned from the ECB reference fix. It could be more complete by naming the response fields or the fix timestamp/date, but for a zero-parameter single-value purchase it is largely sufficient.

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 and there is no parameter meaning for the description to add. Nothing is missing or misleading on this dimension.

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 specific resource and pair: 'USD/PLN exchange rate and inverse, latest ECB reference fix'. An agent can tell it returns both directions of the USD/PLN rate. It does not explicitly distinguish itself from close siblings like buy_fx_pln or buy_fx_usd_eur, leaving the agent to infer pair selection from the 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 rather than stated: the pair and data source make the intent clear, and the payment terms set expectations. However, there is no explicit when-to-use versus the many sibling fx tools (e.g., buy_fx_pln for the inverse-listed pair, buy_fx_eur_pln for the cross), so the agent must reason from names.

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