Skip to main content
Glama

SouthPow crypto & market data

buy_fx_dkk

Paid. Forex rates from DKK to 29 other currencies, 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/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_dkk"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 that calls are paid ($0.005 USDC), the accepted chains (Base or Solana), that no account or API key is required, that failed calls are not charged, and the data source/freshness (latest ECB reference fix). What it omits is the shape of a successful response and whether the listed URL is an alternative REST endpoint.

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?

Extremely tight and front-loaded with 'Paid.' followed by the resource, cost, payment rails, and failure policy. The telegraphic fragments ('$0.005 USDC on Base or Solana', 'No account, no API key') are dense but each earns its place; only the raw URL at the end is slightly awkward as prose.

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-annotation, no-output-schema tool, the description covers purpose, source data, price, payment chains, and failure billing — the things an agent needs before spending money. The main remaining gap is return format and whether a bulk 29-currency response is returned.

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 and there is no parameter meaning the description could or should add. The DKK base and the 29-currency scope are conveyed in prose, which is the only relevant semantic.

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 verb and resource: forex rates from DKK to 29 other currencies, sourced from the latest ECB reference fix. The 'DKK as base, 29 quotes' scope differentiates it reasonably from pair-style siblings like buy_fx_eur_dkk or buy_fx_usd_dkk, though it never names an alternative explicitly.

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 guidance: no mention of when to pick this over buy_fx_eur_dkk, buy_fx_usd_dkk, or the other DKK-related siblings, and no prerequisites beyond noting no account or API key is needed. The scope implies usage but the description never routes the agent.

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