Skip to main content
Glama

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

Africa FX daily brief

get_fx_africa_brief

Africa FX daily brief. Every Frankfurter official African forex pair (shilling, naira, cedi, rand and more) plus both Bybit-derived street quotes (USD-NGN and USD-GHS) and their spreads, each row carrying its source and time. One call for a morning pricing check. Price $0.1 USDC on Base (the /shelf/fx-africa-daily-brief 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.

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

Input Schema

NameRequiredDescriptionDefault
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. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • 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

A3.8/5.0
Behavior4/5

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

With readOnlyHint=false, the description explains why: it spends $0.1 USDC on Base or credits from a valid Shelf Pass, with a specific ≤$0.25 shelf-ceiling rule and a note that the token is not spent above the ceiling. It also discloses the failure mode (payment_required with x402 v2 URL and header name), which annotations alone would not convey.

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 resource and scope, then pricing and auth behavior. The closing sentence ("It does not return the rate as a bare payment link") is a slightly awkward negative framing but still earns its place as a disambiguation.

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?

No output schema, so the description carries the burden and does supply return shape (rows carry source and time; spreads included) and the alternate payment_required response. Complete enough for an agent to know what it gets and what it costs, though it doesn't describe pagination or row volume.

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 meaning beyond the schema for the single pass_token parameter: it names the accepted header (X-SHELF-PASS), the ceiling condition, and the credit-spend consequence -- context the schema hints at but doesn't fully quantify.

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?

States a concrete resource (the full African FX brief: Frankfurter official pairs plus Bybit-derived street quotes and spreads) and its scope, which distinguishes it from the narrower single-source siblings get_fx_official and get_fx_parallel. It doesn't name those siblings, so the differentiation is implied rather than explicit.

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?

"One call for a morning pricing check" gives implied usage, and the payment path (Shelf Pass required above/below ceiling) is spelled out. But it never says when to use this composite brief versus calling get_fx_official or get_fx_parallel, nor any exclusion conditions.

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