Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_dkk

Paid. EUR/DKK 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-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_eur_dkk"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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 disclosure burden and does well: it states this is a paid call ($0.002 USDC), the accepted settlement chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. Missing only freshness/latency beyond 'latest ECB reference fix' and any note on response shape or rate formatting.

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?

Five short sentences, front-loaded with the paid status and the data being sold, then pricing, access conditions, refund policy, and endpoint. No filler; each clause carries distinct information an agent needs before spending money.

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

Completeness5/5

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

For a zero-parameter, no-output-schema price lookup, the description covers everything material: what it returns, the source of the data, cost, payment rails, and billing behavior on failure. There is no schema-level complexity left unaddressed.

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 beyond confirming the pair is fixed by the tool name. Baseline 4 applies for a parameterless tool; the description adds useful context about what the fixed call returns (rate and inverse).

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?

The description names a specific resource and scope: 'EUR/DKK exchange rate and inverse, latest ECB reference fix.' That verb-and-resource pairing plus the stated data source lets an agent separate it from the adjacent buy_fx_eur, buy_fx_dkk, and buy_fx_usd_dkk siblings without opening any schema.

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 implied rather than stated: an agent infers it should call this when it needs the EUR/DKK pair. The description gives no explicit when-not guidance and never names an alternative sibling (e.g., the inverse pair or the USD-based equivalent), so routing between the ~90 buy_fx_* tools is left to inference.

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