Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_hkd

Paid. USD/HKD 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-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_usd_hkd"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 load and does well: it discloses that the call is paid, the exact price, the accepted payment chains, that no authentication is required, and that failures are not billed. It stops short of stating response format, freshness/timestamp, or rate-limit/idempotency behavior.

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?

Six short fragments, cost and scope front-loaded, no filler. The direct endpoint URL is compact and genuinely useful for an agent orchestrating x402-style payments.

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, single-value paid endpoint with no output schema and no annotations, the description covers what it returns (rate and inverse), the data vintage (latest ECB fix), price, and payment rails. Missing only return-shape specifics such as field names and as-of timestamp.

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 semantics to add; the baseline of 4 applies and the description correctly avoids inventing inputs.

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?

Names the exact resource (USD/HKD exchange rate plus its inverse), the underlying data source (latest ECB reference fix), and the access mechanism, which separates it from the dozens of sibling buy_fx_* pair tools at a glance.

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?

Payment terms ($0.005 USDC on Base or Solana, no account or API key, failed calls not charged) tell the agent the cost of invoking it, but there is no explicit guidance on when to prefer this over buy_fx_hkd or buy_fx_eur_hkd — the pair selection is only implied by 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