Skip to main content
Glama

SouthPow crypto & market data

buy_fx_myr

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 well on the dimensions that matter for a paid tool: it states the price ($0.005 USDC), the accepted payment chains (Base, Solana), that no account or API key is needed, and that failed calls are not charged. What it does not disclose is the response shape or freshness/caching behavior, which keeps it short of 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 single most important qualifier ('Paid.') and then one fact per clause with no filler; the endpoint URL is arguably redundant but genuinely useful for an agent. The telegraphic, fragment-heavy style is efficient rather than padded.

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, no-output-schema tool, the description covers what is returned (rates from MYR into 29 currencies), the data source (ECB reference fix), the cost, and the payment path. The remaining gap is that with no output schema, the actual response structure is never described, but the essential call-time information is present.

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; the implicit contract is that it returns all 29 MYR pairs at once, which is consistent with the empty schema. Baseline 4 applies for a no-parameter tool.

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?

The description names a specific resource and scope: 'Forex rates from MYR to 29 other currencies, latest ECB reference fix.' The MYR base is stated up front, which is exactly what separates this from siblings like buy_fx_usd_myr or buy_fx_eur_myr, so an agent can pick correctly without inspecting schemas.

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 scope statement — you use this when you need MYR-based rates — but there is no explicit routing guidance such as 'for a different base currency use the corresponding buy_fx_* tool.' Purchase mechanics (price, chains, no account) are covered, yet the when-to-use-vs-sibling dimension is left to inference.

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