Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_ils

Paid. EUR/ILS 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/eur-ils.

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

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 zero annotations the description carries the full burden and does substantial work: cost ($0.01 USDC), accepted payment chains (Base or Solana), no auth required, and the important billing guarantee that failed calls are not charged. It stops short of disclosing rate limits or quote freshness beyond "latest ECB reference fix," which keeps it from a 5.

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?

Six short sentences, front-loaded with the two things that most affect an agent's decision — that it is paid and what data it returns. Cost, prerequisites, billing behavior, and endpoint URL each appear once with no restatement.

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-annotation, no-output-schema endpoint, the definition covers what an agent needs: what it returns, what it costs, how to pay, and that failures are free. The only real omission is the response shape (field names for rate and inverse), which matters somewhat since no output schema is published.

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 no parameters, so the schema has nothing to explain and the baseline is 4. The description correctly implies the call is fully determined by the tool name — no pair, date, or amount arguments are mentioned or needed.

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 (EUR/ILS exchange rate), states it returns the inverse as well, and pins the data source to the latest ECB reference fix. Against a sibling list containing buy_fx_eur_aud, buy_fx_usd_ils and buy_fx_ils, this unambiguously identifies the correct pair and base currency.

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?

Prerequisites are covered ("No account, no API key") and the paid gating is stated up front, so an agent knows the call is billable. However, there is no explicit guidance on when to pick this pair tool over the nearby buy_fx_ils or buy_fx_eur siblings, or on caching/refresh expectations — selection is left to inference from the pair name.

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