Skip to main content
Glama

SouthPow crypto & market data

buy_fx_sgd

Paid. Forex rates from SGD to 29 other currencies, 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/sgd.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 behavioral load and does it reasonably well: it discloses that the call is paid ($0.01 USDC on Base or Solana), requires no account or API key, that failed calls are not charged, and that the data source is the latest ECB reference fix. Missing are response shape, rate date/timestamp semantics, and update cadence.

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?

Telegraphic but front-loaded and waste-free: payment, scope, cost, auth model, failure policy, endpoint. The raw URL is the weakest element for an agent's decision-making, but it is short and does no real harm.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-param, no-output-schema tool, the description covers what is fetched, its provenance, its cost and its payment rails. It leaves the agent guessing about the return structure (per-currency rows? single object? which currency codes?) and whether the rates carry an effective date, which matters for a reference-rate product.

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 meaning to convey and the baseline applies. The description adds that the returned set covers 29 currencies rather than a single pair, which is the closest thing to an input/scope clarification available here.

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 SGD to 29 other currencies, latest ECB reference fix.' This disambiguates it from the hundreds of buy_coin_* siblings and from the inverse pairs like buy_fx_usd_sgd and buy_fx_eur_sgd, since it explicitly says the base is SGD. It stops short of naming those sibling pairs as the alternative for other base currencies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance. In a family this large (buy_fx_usd_sgd, buy_fx_eur_sgd, buy_fx_usd, buy_fx_eur, plus 29-per-base variants), the description never tells the agent which of these to pick for a given currency pair, nor whether results are cacheable.

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