Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_isk

Paid. EUR/ISK exchange rate and inverse, latest ECB reference fix. $0.005 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/forex-rates/eur-isk.

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

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 supplied, the description carries the full behavioral burden and does real work: it discloses that the call is metered, the exact price and accepted payment chains, the absence of auth, and that failed calls are free — all facts an agent needs before spending. It also identifies the upstream source (ECB reference fix), which implies daily-fix freshness, though it doesn't state the update cadence or any rate limit explicitly.

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 clauses, front-loaded with the payment signal 'Paid.' so cost is visible before anything else. Every clause adds a distinct fact (data, price, chain, auth, failure policy, endpoint) with no repetition or filler.

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-param, no-output-schema tool, the description supplies cost, payment method, auth requirements, failure billing, data provenance, and the returned measures — enough to decide and invoke correctly. The remaining gap is the response structure and the fix cadence/staleness window, which an agent might still want given there is no output schema to consult.

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 argument semantics to explain and the baseline applies. The description correctly avoids inventing inputs and instead specifies output content (rate and inverse), which is the only variable an agent could otherwise wonder about.

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?

The description names the exact resource (EUR/ISK exchange rate plus its inverse) and the data source (latest ECB reference fix), so an agent can tell it apart from the many other buy_fx_* pair tools by currency pair alone. It stops short of explicitly contrasting itself with buy_fx_eur, buy_fx_isk, or buy_fx_usd_isk, so a reader infers rather than reads the differentiation.

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?

It covers the practical prerequisites for calling: cost ($0.005 USDC on Base or Solana), no account or API key, and no charge on failure, which tells the agent this is a viable unauthenticated call. However, it never says when to prefer this over the sibling pair tools (buy_fx_eur for all EUR rates, buy_fx_isk, or buy_fx_usd_isk for the USD cross), so pair selection is left to inference.

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