Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_cny

Paid. USD/CNY 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/usd-cny.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 the paid nature, exact price ($0.01 USDC), accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It omits rate limits, caching/freshness window, and response shape, which keeps it from a 5.

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?

Front-loaded with the billing flag and then the payload, with no filler sentences. The telegraphic fragments ('Paid.') are efficient though slightly clipped, and the raw URL at the end is more reference than guidance.

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-param, annotation-free tool with no output schema, the description covers cost, payment method, authentication, failure handling, and data provenance, and hints at return content ('rate and inverse'). The main remaining gap is what the payload actually looks like (fields, timestamp of the fix).

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; baseline 4 applies. The description correctly implies no inputs are needed by stating 'No account, no API key'.

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?

Names the exact resource ('USD/CNY exchange rate and inverse') and the data source ('latest ECB reference fix'), so an agent can tell it apart from buy_fx_cny or buy_fx_usd_eur by the currency pair. It stops short of explicitly contrasting itself with the nearest siblings, so a 4 rather than 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?

Usage is only implied by the pair name; there is no statement of when to pick this over buy_fx_cny, buy_fx_eur_cny, or the generic buy_fx_usd, and no exclusions or prerequisites beyond payment. An agent can infer intent but must reason about sibling choice itself.

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