Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_dkk

Paid. USD/DKK exchange rate and inverse, latest ECB reference fix. $0.005 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/forex-rates/usd-dkk.

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

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 supplied, the description carries the full burden and does well: it discloses cost, accepted payment rails, absence of auth setup, the billing guarantee ('Failed calls not charged'), and the underlying data source/freshness ('latest ECB reference fix'). Gaps remain on rate limits and staleness cadence for the daily ECB fix.

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?

Telegraphic fragments, but each carries payload: price, rails, auth, billing guarantee, data source, endpoint. Nothing is padded. The raw URL is marginal information for an agent that has no parameters to send and slightly dilutes the front-loaded value statements.

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-param, no-output-schema purchase tool, the description covers what an agent most needs: what is returned (rate plus inverse), the source, the cost, how to pay, and that failures are free. Remaining shortfalls are response shape and refresh cadence, which matter only for downstream parsing.

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 and the baseline of 4 applies. The description correctly implies the output pair is fixed rather than caller-selectable, which prevents an agent from trying to pass a currency argument.

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 concrete resource and data source: 'USD/DKK exchange rate and inverse, latest ECB reference fix.' An agent knows exactly what it gets and from where. It does not, however, state how it differs from the ~200 sibling currency-pair tools (e.g. buy_fx_usd_eur or buy_fx_dkk), leaving the pair selection implicit in the name.

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?

The description gives decision-relevant prerequisites — 'Paid. $0.005 USDC on Base or Solana. No account, no API key.' — which helps an agent judge whether it can afford/access the call. But there is no explicit when-to-use guidance, no mention of alternatives for other pairs, and no fallback if payment is unavailable.

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