Skip to main content
Glama

SouthPow crypto & market data

buy_fx_hkd

Paid. Forex rates from HKD 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/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_hkd"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full burden and does it well: it discloses that the call costs money, the exact price and accepted payment chains (Base or Solana), that no auth is required, that failed calls are not charged, and that the data is the ECB reference fix. What is missing is response shape and freshness/caching cadence, which matters for a rate feed.

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?

Telegraphic and front-loaded — 'Paid.' leads, followed by what it returns, then cost, then access terms, then the endpoint URL. No sentence is filler, and an agent can extract the cost and auth profile from a single skim.

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 paid endpoint with no annotations and no output schema, the definition covers cost, payment rail, auth, data source, coverage, and failure billing — everything needed to decide and call. The one real gap is that with no output schema, the description never hints at the response format an agent should expect to parse.

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 nothing in the description drags it down. The mention of '29 other currencies' usefully tells the agent the coverage breadth without implying any input it must supply.

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 resource and direction: 'Forex rates from HKD to 29 other currencies, latest ECB reference fix.' The 'from HKD' base-currency framing is what separates it from siblings like buy_fx_usd_hkd or buy_fx_eur_hkd. It does not explicitly name those siblings as alternatives, which keeps it from a 5.

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?

'Paid' and the $0.005 price give an agent a cost signal before calling, and 'no account, no API key' removes setup questions. But there is no explicit when-to-use/when-not guidance — nothing tells the agent to prefer buy_fx_eur_hkd instead if it needs a EUR base, or how this relates to the buy_crypto_price / buy_fx_usd_* family. Usage is implied by the currency pair only.

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