Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_sek

Paid. EUR/SEK 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-sek.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full behavioral burden and does well: it discloses that the call is paid at $0.01 USDC on Base or Solana, requires no account or API key, and that failed calls are not charged. It leaves the response shape and update cadence of the ECB fix unspecified.

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 fragments, front-loaded with the payment flag, with zero filler or repetition. Every clause (price, chains, auth, failure billing, endpoint) adds information an agent or its payer needs.

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 purchase tool, the definition covers what is fetched, where it comes from, what it costs, and how to pay, which is most of what is needed. It stops short of describing the returned fields (rate vs inverse) or the freshness of the fix.

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; there is nothing for the description to disambiguate. The embedded endpoint URL usefully confirms no query parameters are expected.

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 exact resource (EUR/SEK rate plus its inverse) and the data source (latest ECB reference fix), so an agent knows precisely which currency pair it buys. It never explicitly contrasts itself with near-identical siblings like buy_fx_sek or buy_fx_eur, relying on the pair name alone for disambiguation.

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?

There is no when-to-use or when-not-to-use guidance: nothing says to prefer buy_fx_eur_sek over buy_fx_sek, buy_fx_usd_sek, or a free alternative, and no mention of when the fix goes stale. The payment terms hint that this is a paid call, but that is incidental rather than routing guidance.

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