Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_krw

Paid. EUR/KRW 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-krw.

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

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 supplied, the description carries the full burden and does solid work: it states the tool is paid ($0.002 USDC), names the payment networks (Base or Solana), says no account or API key is needed, and that failed calls are not charged. The remaining gaps are the shape and freshness of the payload, which are not covered anywhere else.

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?

Six short fragments, front-loaded with 'Paid' so the cost signal comes before anything else, then the data, then payment mechanics. Nothing in it is filler for a tool this simple.

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?

Given zero parameters, no annotations, and no output schema, the description covers the essentials an agent needs: what the data is, what it costs, how to pay, and that failures are free. It leaves the response shape and staleness of the ECB fix unstated, and the trailing URL is ambiguous as to whether it is documentation or a callable endpoint.

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. The description adds one useful return-side detail, that the inverse rate is included alongside the pair, which the empty schema cannot convey.

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?

Names a specific resource pair and scope: 'EUR/KRW exchange rate and inverse, latest ECB reference fix.' That tells an agent exactly which data it returns and that the source is the ECB reference fix. It stops short of distinguishing itself from near-neighbours such as buy_fx_krw or buy_fx_eur, so the agent must infer the difference from the pair name alone.

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: 'latest ECB reference fix' quietly signals a reference rate rather than a live market tick, which is genuine selection context. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. buy_fx_krw, buy_fx_usd_krw), so the agent gets no routing 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