Skip to main content
Glama

SouthPow crypto & market data

buy_fx_idr

Paid. Forex rates from IDR to 29 other currencies, latest ECB reference fix. $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/forex-rates/idr.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 disclosure burden and does well: it declares that the call is paid, the exact price ($0.002 USDC), the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. That last point matters for a paid tool because it bounds the downside of retries. Rate limits and response shape are not covered, which keeps it out of the 5s.

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?

Six short sentences, front-loaded with the payment status and price, so an agent can stop reading as soon as it knows the cost. The telegram style ('Paid.', bare URL at the end) is terse but not padded. Slightly more connective phrasing would have helped the payment terms read as one coherent thought.

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

Completeness5/5

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

This is a zero-parameter paid data fetch. Payment terms, chains, auth requirements, failure billing, data source, and the endpoint URL are all disclosed. No output schema exists, but the description names the payload (rates from IDR to 29 currencies, ECB fix), which is enough for an agent to know what it gets back. Nothing critical is missing.

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 the baseline is 4. There is nothing for the schema to explain and nothing the description needs to add.

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: IDR-base forex rates covering 29 currencies from the ECB reference fix. That is enough to separate it from EUR-base siblings like buy_fx_eur_idr and USD-base ones like buy_fx_usd_idr. It stops short of naming those alternatives, so the differentiation rests on the agent reading the currency convention itself.

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?

There is no explicit when-to-use or when-not-to-use guidance. An agent must infer that this is the tool to pick when the base currency is IDR. Across roughly 600 near-identical buy_fx_* siblings, a sentence such as 'use this only for IDR-based rates; for USD-based rates use buy_fx_usd_idr' would have been worth a lot.

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