Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_pln

Paid. EUR/PLN 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/eur-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_eur_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, the description usefully discloses the $0.002 USDC price, Base or Solana payment options, lack of account/API-key requirements, and that failed calls are not charged. It does not explain payment authorization, ECB publication timing, or freshness beyond “latest.”

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?

The description is compact and front-loads both its paid nature and the exact data supplied. Cost, networks, authentication, failure billing, and endpoint each add practical information without unnecessary elaboration.

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 lookup, it covers the resource, source, price, payment networks, authentication, failure charging, and endpoint. Because there is no output schema, response fields and rate-fix timestamp or freshness semantics would still be useful, and sibling selection remains implicit.

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 has no parameters, so there is no parameter-documentation burden and the baseline score applies. The fixed pair-specific URL reinforces that the operation requires no user-supplied options.

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?

The description identifies the exact data product—EUR/PLN and its inverse—and specifies the latest ECB reference fix as its source. It lacks an explicit retrieval verb and does not distinguish itself from close siblings such as buy_fx_pln or buy_fx_usd_pln, so it is clear but not fully discriminating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear usage context: this is suitable when the latest ECB EUR/PLN reference fix and inverse are sufficient and a paid call is acceptable. It gives no explicit exclusions or alternative tools for other pairs or different rate requirements.

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