Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_thb

Paid. EUR/THB 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-thb.

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

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 present, the description carries the full burden and does a solid job: it discloses that the call is paid, the exact price and accepted chains, that no account or API key is required, that failed calls are not charged, and the underlying data source (ECB reference fix). It stops short of describing freshness/caching, rate limits, or the response payload shape, which are the remaining behavioral gaps.

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?

Five short, front-loaded fragments: payment status first, then data content and source, then cost/chains, then auth and failure policy, then endpoint. No redundant restatement of the title or name, and every clause (price, chains, no-account, no-charge-on-failure) conveys decision-relevant information.

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, single-shot paid fetch with no annotations and no output schema, the definition covers what is returned (spot rate and inverse from ECB), what it costs, how payment works, and what happens on failure. The main omission is any indication of the actual returned payload structure or quote freshness, which matters because no output schema exists to compensate.

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 for the description to disambiguate. The description's note that the response includes both the rate and its inverse adds useful output context even though it is not a parameter concern.

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 a specific data resource (EUR/THB exchange rate plus its inverse, sourced from the latest ECB reference fix), so an agent knows exactly what it is buying. It does not explicitly contrast itself with the many adjacent pair tools (buy_fx_eur, buy_fx_thb, buy_fx_usd_thb), so the differentiation is left to the tool name.

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?

The description supplies cost and payment context ('$0.005 USDC on Base or Solana', 'no account, no API key', 'failed calls not charged') that helps an agent decide whether the call is worth making. However, it never states when to prefer this pair-specific tool over single-currency siblings like buy_fx_eur or buy_fx_thb, so selection guidance is only implied by 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