Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_jpy

Paid. EUR/JPY 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-jpy.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations supplied, the description still discloses the $0.01 USDC charge, supported Base and Solana networks, lack of account or API-key requirements, and the policy that failed calls are not charged. The ECB source and latest-fix behavior add further useful operational context.

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?

The description is compact and front-loads the paid nature and exact data provided. Pricing, authentication, failure charging, and the endpoint each add useful information without digression.

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?

This is nearly complete for a zero-input paid lookup: an agent can determine the resource, source, cost, and basic invocation requirements. Because there is no output schema, the main remaining gaps are the response shape and timestamp fields, plus more precise ECB publication or refresh timing.

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 has no parameters, so there is no input syntax or option behavior requiring explanation. The description and endpoint adequately establish that the currency pair is fixed rather than caller-configurable.

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 identifies the exact data product: the EUR/JPY rate, its inverse, and the latest ECB reference fix. The fixed pair distinguishes it from other buy_fx_* tools, although an explicit retrieval verb would make the action clearer.

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 for obtaining a current ECB reference rate rather than an unspecified exchange-rate quote. It does not explicitly explain when to choose this cross-rate tool over siblings such as buy_fx_eur or buy_fx_jpy, or clarify that the reference fix should not be treated as a live trading price.

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