Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_nok

Paid. USD/NOK 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-nok.

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

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 fair job: it discloses cost ($0.01 USDC), accepted chains (Base or Solana), that failed calls are not charged, that no auth is needed, and that values come from the latest ECB reference fix. It omits return shape, freshness granularity (how often the fix updates), and any rate limiting, so it is informative but not exhaustive.

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?

The text is short, front-loaded with the most decision-relevant fact ('Paid.'), and each clause adds new information: what, price, rails, auth, billing behavior. The trailing raw endpoint URL is marginal for an agent but harmless, and the telegraphic style occasionally reads as a price tag rather than prose.

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 paid lookup with no output schema and no annotations, the description covers the essentials an agent needs before invoking: cost, payment method, absence of auth, billing on failure, and data provenance. What is missing is only the response structure and refresh cadence, which are nice-to-have rather than blocking.

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, which is the baseline-4 case; there is nothing the schema needs the description to compensate for. The description implicitly confirms no inputs are required by stating no account or API key is needed, though it does not explicitly say the call takes no arguments.

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 a specific resource and scope: USD/NOK exchange rate plus its inverse, sourced from the latest ECB reference fix. That clearly separates it from the hundreds of buy_coin_* and buy_yields_* siblings, but it never explicitly contrasts with the adjacent buy_fx_nok or buy_fx_eur_nok variants, leaving the agent to infer the distinction from the name alone.

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 is implied rather than stated: the leading 'Paid.' plus the price and payment rails signal this is a paid lookup, and 'No account, no API key' removes setup prerequisites. There is no explicit when-to-use statement, no guidance on preferring buy_fx_nok versus this pair tool, and no note about caching or rate limits for repeated calls.

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