Skip to main content
Glama

SouthPow crypto & market data

buy_fx_krw

Paid. Forex rates from KRW 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/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_krw"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 most of it: it discloses the payment model, exact price, accepted chains, absence of auth requirements, the refund policy for failed calls ('Failed calls not charged'), and the authoritative data source (ECB reference fix, i.e. a once-daily fix, not live ticking). It does not describe the response payload shape, which is the main remaining gap since no output schema exists.

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?

Six short sentences, telegraphic and front-loaded with the fact that this is a paid call, followed by data scope, price, and access terms. Dense but every sentence carries information; only the trailing URL is arguably redundant with the tool's own routing.

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?

No parameters and no output schema mean the description must convey scope and cost, and it does: what data (29 KRW-quoted rates), how fresh (ECB reference fix), how much, how to pay, and that failures are free. Only the shape of the returned rate listing is left unspecified, which is a modest omission for this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 to disambiguate and the baseline of 4 is exceeded by the description implicitly confirming the fixed base currency and fixed quote set, removing any expectation that currency codes can be passed in.

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 the resource (forex rates), the base currency (KRW), the quote side (29 other currencies), and the data source (latest ECB reference fix). That base-currency wording distinguishes it from the crowded buy_fx_eur_krw / buy_fx_usd_krw siblings which return the same pair from the other direction.

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?

Prerequisites are covered well (paid, $0.01 USDC on Base or Solana, no account or API key), which tells an agent whether it can call this at all. But there is no explicit when-to-use or when-to-prefer-an-alternative guidance relative to the ~100 other buy_fx_* tools, so selection still relies on the agent inferring from the base currency.

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