Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_hkd

Paid. EUR/HKD 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/eur-hkd.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 a solid job: it discloses that the call is paid, the exact price ($0.01 USDC), accepted payment networks (Base or Solana), that no auth is required, and that failed calls are not charged. Gaps remain around rate limits, caching/freshness cadence, and what happens on partial payment failure, but the commercial and auth profile is unusually well covered.

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, front-loaded fragments with no filler; the payment and auth facts lead and the endpoint URL trails. The raw URL is mildly redundant with the tool's invocation path but is plausibly useful for an HTTP-based paid-call flow, so it earns most of its space.

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?

There is no output schema, so the description has to convey the return payload, and it only partially does: it says rate plus inverse from the ECB fix but not the response shape, timestamp field, or decimal precision. For a zero-param purchase endpoint the commercial details are complete, but the returned data contract remains under-specified.

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 no parameter meaning for the description to add; the baseline for a parameterless schema applies. Nothing in the description misleads about inputs.

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?

The description names the exact resource (EUR/HKD exchange rate plus its inverse) and the data provenance (latest ECB reference fix), which is far more specific than the tool name alone. It does not explicitly differentiate itself from sibling pairs like buy_fx_eur or buy_fx_hkd, but the currency pair in the name plus the stated source makes the target unambiguous.

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 by the pair specification and the 'Paid' framing, and the description adds useful purchase context (cost, accepted payment chains, no account or API key needed). However, it never states when to prefer this over a related sibling pair tool or whether a non-paid alternative exists, so selection guidance is inferred rather than explicit.

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