Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_myr

Paid. USD/MYR 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-myr.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does a decent job: it discloses that the call is paid ($0.005 USDC on Base or Solana), that no auth is required, and that failures are not charged — all critical for an agent deciding whether to spend. It omits output shape and any rate-limit or freshness/staleness caveats beyond 'latest ECB reference fix'.

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?

Roughly five short clauses, front-loaded with the 'Paid' signal and the core resource — an agent can stop reading after sentence one if cost is a blocker. The telegraphic style (sentence fragments, bare URL) is efficient but slightly clipped, and the endpoint URL is marginally redundant with the tool name.

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?

With no annotations, no output schema, and zero parameters, the description supplies what an agent actually needs: the data returned, the source, the cost, the payment chains, and the no-auth/no-charge-on-failure terms. The only real gap is the response format (field names, whether inverse and direct are separate fields), which an agent must discover empirically.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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; the schema is empty and the description adds no false parameter expectations. Baseline for a 0-param tool is 4, and the description goes slightly further by pinning the exact pair and fixing source in place of parameters.

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 data source: 'USD/MYR exchange rate and inverse, latest ECB reference fix', which tells an agent exactly what value it returns. The currency pair is embedded in the name and restated, but the description never distinguishes it from the neighboring buy_fx_usd, buy_fx_myr, or buy_fx_eur_myr endpoints, leaving sibling selection to inference.

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?

Prerequisites are covered well (no account, no API key, failed calls not charged), which tells an agent it can call freely without setup. However, there is no explicit when-to-use-vs-alternative guidance — nothing says when to prefer this over buy_fx_usd or buy_fx_eur_myr, so the agent must infer from naming conventions.

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