Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_chf

Paid. EUR/CHF 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-chf.

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

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, the description carries the full burden and does well: it discloses the paid model, the exact price ($0.002 USDC), the accepted rails (Base or Solana), the absence of auth, and that failed calls are not billed. It stops short of explaining how payment is actually settled or what the response body looks like, which is the remaining behavioral gap.

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-loaded with the most decision-relevant fact ('Paid.') then price, rails, and endpoint in a tight fragment-based format with zero filler. The bare URL trailing the sentence is slightly awkward but serves as a de facto endpoint identifier.

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 purchase tool, the agent needs cost, payment rails, auth requirements, and what data comes back — all of which are present. The only omission is any sense of return shape or update cadence, which matters somewhat for a rate feed but not enough to block correct invocation.

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; the baseline applies. The description correctly implies no input is needed beyond payment.

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 (EUR/CHF exchange rate plus its inverse) and its provenance (latest ECB reference fix), which is far more than the name alone conveys. It does not explicitly point at sibling pair tools such as buy_fx_chf or buy_fx_eur, but the pair-specific naming makes mis-selection unlikely.

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 gives access conditions (no account, no API key, failed calls not charged) which imply usage is frictionless, but never states when to choose this pair tool over the broader single-currency siblings or what happens with stale/market-closed data. Usage is inferable from the pair name rather than guided by the text.

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