Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_sgd

Paid. USD/SGD 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-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_usd_sgd"
  }
}

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 supplied, the description carries the whole burden and does a solid job: it discloses that the call is paid, the exact price and accepted payment chains, that no auth or account is required, and that failures are not billed. It stops short of five because it says nothing about rate freshness/staleness (ECB fixes are published once per business day) or any rate limits, which materially affect how an agent should use the value.

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 30 words that are entirely load-bearing: what, source, price, chains, auth, billing behavior, endpoint. The telegraphic fragments ('Paid.', 'No account, no API key.') read as clipped but keep the critical payment terms front-loaded before the URL.

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, no-output-schema paid endpoint, the description covers the things an agent actually needs to decide and transact: data source, price, settlement chains, and failure billing. The main residual gap is response freshness and cadence — whether the returned fix is today's or possibly stale on weekends/holidays.

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 a parameterless call with no inputs to supply.

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?

Names the exact resource and pair ('USD/SGD exchange rate and inverse') plus the data source ('latest ECB reference fix'), which cleanly separates it from buy_fx_sgd (SGD base) and buy_fx_eur_sgd (EUR cross). An agent can pick this over the hundreds of buy_fx_* siblings without opening any schema.

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 context is implied by the pair name and made concrete on the commercial side ('$0.01 USDC on Base or Solana', 'no account, no API key', 'failed calls not charged'). However, there is no explicit statement of when to choose this versus buy_fx_sgd or buy_fx_usd, nor any note that it returns a daily reference fix rather than a live quote — the agent must infer selection from naming convention alone.

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