Skip to main content
Glama

SouthPow crypto & market data

buy_fx_inr

Paid. Forex rates from INR 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/inr.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is needed, and critically that failed calls are not charged — a real behavioral guarantee an agent must know before spending. It omits payment mechanics and whether the ECB fix is daily-updated, which keeps it just short of top marks.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the cost signal ('Paid.') and then the data, price, prerequisites, and pricing URL in a tight sequence with no filler. Every clause — cost, source, chains, auth, failure policy, endpoint — carries information.

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 tool this covers the essentials: what data comes back (INR to 29 currencies, latest ECB reference fix), cost, payment chains, and auth posture. The gap is operational — it never explains how to actually settle the $0.01 USDC payment or what the response payload looks like.

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?

There are zero parameters, so the baseline is 4 and there is no parameter meaning left to convey. Nothing in the description is needed to help an agent fill in the call.

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?

States a specific verb and resource pair — 'Forex rates from INR to 29 other currencies' — with the base currency (INR) and breadth (29 currencies) made explicit. The INR base cleanly distinguishes it from the many buy_fx_usd_* and buy_fx_eur_* siblings, so an agent can select it without opening the 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?

The description implies the use case (fetch INR-based FX rates) and gives prerequisites ('No account, no API key'), but never states when to choose this over the alternatives such as buy_fx_usd_inr or buy_fx_eur_inr, nor any when-not condition. The agent must infer that the INR base is the sole selection criterion.

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