Skip to main content
Glama

Ni Biashara Shelves — Africa FX, freight & compliance checks (x402)

Official FX rates — all eight pairs

get_fx_official_all
Read-only

Official FX rates — all eight pairs. All eight official African exchange rates vs USD in one payload (Kenyan, Tanzanian and Ugandan shilling, naira, cedi, rand, Egyptian pound, Rwandan franc), via Frankfurter (frankfurter.dev). Same blend and the same as_of / source fields as the single-pair shelf. $0.02 USDC on Base. Returns the x402 URL to GET (402 → PAYMENT-SIGNATURE → delivery). Free to call this tool; payment happens on the URL.

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": "get_fx_official_all"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say it is a safe, open-world read; the description adds the economically decisive facts an agent cannot infer from them: it costs $0.02 USDC on Base, calling the tool itself is free, and the tool returns an x402 URL that must be GET'd with a 402 → PAYMENT-SIGNATURE → delivery handshake. It also names the upstream source (Frankfurter) and states field-shape consistency with the single-pair tool.

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?

It is dense but front-loaded with the payload scope, then cost, then delivery mechanics — the right order for an agent deciding whether to call. There is mild redundancy between the title echo ('all eight pairs') and the first sentence's restatement, and the long parenthetical currency list could be trimmed, but nothing is genuinely wasted.

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?

With no parameters and no output schema, the description carries the full burden and discharges it: it specifies coverage, source, field parity with the sibling, price, and the exact mechanism by which the agent obtains data after paying. Nothing an agent needs in order to decide to call — or to handle the result — is missing.

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, and the baseline of 4 applies. The description appropriately uses its limited space for the return/payment contract instead of inventing parameter guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb/resource (fetch all eight official African FX rates vs USD) and enumerates the exact currencies covered. It also distinguishes itself from the sibling get_fx_official by noting it returns 'the same blend and the same as_of / source fields as the single-pair shelf,' so an agent can tell the batch version from the single-pair version without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear context for use — pull all eight pairs 'in one payload' rather than repeatedly calling the single-pair tool — and names the comparison point (single-pair shelf). It stops short of an explicit 'use this when X, use get_fx_official when Y' rule, and it never contrasts with get_fx_parallel or get_fx_africa_brief, which are the other plausible alternatives.

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