Skip to main content
Glama

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

by biz.nibiashara
OverviewDiscussionsAdmin

Official FX rate — one African pair

get_fx_official

Official FX rate — one African pair. Official reference rate vs USD for one of KES, NGN, GHS, TZS, UGX, ZAR, EGP, RWF, via Frankfurter (frankfurter.dev). Frankfurter blends published central-bank reference rates; the number is that blend, not a single central-bank fixing. Each response names the source and carries as_of (Frankfurter's rate date) and fetched_at. Price $0.01 USDC on Base (the /shelf/fx-official price). With a valid Shelf Pass (pass_token or X-SHELF-PASS) on a shelf priced ≤ $0.25, this returns the data. Otherwise it returns payment_required with the x402 v2 URL and header name. It does not return the rate as a bare payment link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pairYese.g. USD-KES (required)
pass_tokenNoShelf Pass token (pass_…). On an eligible shelf the tool returns the data and spends credits. Above the pass ceiling the token is not spent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / pass_token
      Added value: +{
+  "description": "Shelf Pass token (pass_…). On an eligible shelf the tool returns the data and spends credits. Above the pass ceiling the token is not spent.",
+  "type": "string"
+}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

The readOnlyHint=false annotation is ambiguous on its own, but the description explains why: the call spends credits/charges $0.01 USDC and can return payment_required with an x402 URL. It also discloses that the rate is a central-bank blend rather than a single fixing, and that responses carry source, as_of, and fetched_at. This is rich behavioral context well beyond the annotations.

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?

Front-loaded with the purpose, then progressively discloses source methodology and payment semantics. Dense but every sentence carries information; it is slightly long for a one-rate lookup.

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?

Despite no output schema, the description specifies what the response contains (source, as_of, fetched_at) and what failure returns (payment_required with x402 URL/header). Payment prerequisites and eligibility ceiling are all covered, so nothing needed to call it correctly 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real value by enumerating the eight valid currencies for `pair` and clarifying that pass_token is the in-band alternative to the X-SHELF-PASS header. It does not add pair-format syntax beyond the schema's example.

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?

States a specific verb (get/return), resource (official FX rate), and scope (one African pair vs USD) and names the source (Frankfurter) plus the eight supported currencies. An agent can distinguish it from get_fx_parallel and get_fx_africa_brief by the word 'official' and the single-pair scope.

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?

It explains the gating conditions (pass_token / Shelf Pass ≤ $0.25 returns data, otherwise payment_required), which is useful context, but never explicitly says when to pick this over get_fx_parallel or get_fx_africa_brief. Usage is only implied by 'official'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ni Biashara Shelves — Africa FX, freight & compliance checks (x402) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources