Skip to main content
Glama

SouthPow crypto & market data

buy_fx_sek

Paid. Forex rates from SEK to 29 other currencies, 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/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_sek"
  }
}

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 burden and does well: it discloses that the call is paid ($0.005 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It does not describe the response shape, rate freshness window beyond 'latest', or latency, which are the remaining gaps.

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?

Six short clauses with no redundant wording, and the cost-relevant facts ('Paid', price, payment rail) are front-loaded before the data description. The final URL clause is functional but adds a slightly fragmented tail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 with no annotations, the description covers everything an agent needs before calling: what data, from what source, at what price, on which chains, with what auth and failure-billing behavior. No material gap remains.

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 nothing for the description to disambiguate; baseline is 4. The description instead pins down the fixed semantics of the call (base currency SEK, 29 quote currencies, ECB fix), which is the right use of the space.

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 specific resource (forex rates), the exact base currency direction (from SEK to 29 other currencies), and the data provenance (latest ECB reference fix). An agent can distinguish this from the EUR- or USD-based cross-rate siblings by the stated base currency, though no sibling is named explicitly.

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?

Usage context is implied by the currency direction, and cost/auth constraints are stated, but there is no explicit 'use this when' instruction or comparison against buy_fx_eur_sek / buy_fx_usd_sek for the same SEK pair. The agent must infer selection from the base currency alone.

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