Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_krw

Paid. USD/KRW 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-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_usd_krw"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description does real work: it discloses the pay-per-call model ($0.01 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. What it omits is freshness cadence (how stale the ECB fix can be, weekend/holiday behavior) and any rate limiting, which matter for a priced data call.

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 'Paid.' and packed with decision-relevant facts in four short sentences with no filler. The trailing endpoint URL is mildly redundant with the tool's own identity but is not harmful; the telegraphic fragments read less cleanly than full sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple zero-parameter tool this covers cost, payment chain, auth, and failure policy well. However, with no output schema present, the description should say more about what the response contains (field names, inverse calculation, timestamp of the fix) than the single phrase 'exchange rate and inverse'.

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 and the description correctly introduces none, instead fully specifying the currency pair and data source in prose. Baseline 4 applies since there is nothing in the schema requiring clarification beyond confirming the pair is fixed.

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 (USD/KRW exchange rate and its inverse) and names the data source (latest ECB reference fix), so the agent knows exactly what is fetched. It does not distinguish itself from the closely related siblings buy_fx_krw or buy_fx_eur_krw, which an agent could easily confuse it with given the near-identical naming across hundreds of fx tools.

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

Usage Guidelines2/5

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

There is no when-to-use, when-not-to-use, or alternative guidance. The 'latest ECB reference fix' phrase hints the rate is a daily reference rather than a live quote, but the description never tells the agent to prefer a different sibling for intraday rates or for a different base currency, so selection among the many fx tools is left entirely to the name.

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