Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_idr

Paid. USD/IDR exchange rate and inverse, 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/usd-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_usd_idr"
  }
}

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, the description carries the full burden and does well on the commercial side: it discloses the price ($0.002 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It does not say how fresh the fix is or what the response payload looks like, which is the main remaining gap.

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-loading "Paid." immediately signals the cost model, then each clause adds a distinct fact (data, price, chains, auth, failure policy, endpoint). Slightly telegraphic, but there is no filler and no repetition.

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-parameter fetch with no output schema, the description should sketch the return shape (e.g., rate value, inverse, as-of timestamp) since nothing else documents it. It covers billing and access fully but leaves the output contract entirely unstated.

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 and there is nothing for the description to disambiguate. The embedded endpoint URL confirms the pair is pinned in the route rather than passed as an argument.

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?

"USD/IDR exchange rate and inverse, latest ECB reference fix" names the exact resource, the direction plus inverse, and the data source, which distinguishes it from the broad buy_fx_usd or buy_fx_idr siblings. There is no explicit verb (fetch/return), though the intent is unmistakable.

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?

The description gives no when-to-use guidance and never names an alternative. An agent facing both buy_fx_usd_idr and buy_fx_idr (or buy_fx_usd_eur) must infer the difference from the tool name alone, with no statement of which pair orientation to pick.

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