Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_inr

Paid. USD/INR 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-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_usd_inr"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 a good job: it discloses the monetization model ($0.01 USDC on Base or Solana), the lack of authentication requirement, and the billing behavior on failure. It also states the underlying data source and that it is the latest fix, though it says nothing about response format, caching, or latency.

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-loaded with the payment flag, then resource, cost, access conditions, and endpoint — a sensible priority order with no filler sentences. The telegraphic style ('Paid.', 'No account, no API key.') is efficient, though the raw URL at the end is more useful to a paywall client than to a selecting agent.

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 parameterless paid data endpoint with no annotations and no output schema, the description covers cost, payment rails, auth posture, failure behavior, and data provenance. The main residual gap is the shape of the returned rate payload, which an agent must discover by calling.

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 add and the baseline of 4 applies. The description correctly does not waste space re-describing inputs that do not exist.

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?

Names the concrete resource (USD/INR exchange rate, plus its inverse) and the data source (latest ECB reference fix), which is more specific than the sibling names alone convey. It does not explicitly distinguish itself from near-neighbors like buy_fx_inr or buy_fx_usd_eur, so an agent must infer the pair convention from the catalog rather than from the text.

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 supplies pay-to-use context (cost, accepted chains, no account or API key, no charge on failure), which implicitly answers 'when is this callable' but not 'when should this be chosen over another FX tool'. There are no explicit exclusions or routing hints toward buy_fx_inr or the cross-rate siblings.

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