Skip to main content
Glama

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

Parallel-rate history — last 24 hours, hourly

get_fx_parallel_history_24h
Read-only

Parallel-rate history — last 24 hours, hourly. Hourly street-rate mid/buy/sell, spread and depth for USD-NGN (naira) or USD-GHS (cedi) from Ni Biashara's own archive of the Bybit-derived quote. Each point is the hour the book was captured. $0.1 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pair": "<pair>"
    },
    "name": "get_fx_parallel_history_24h"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairYesUSD-NGN or USD-GHS (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations cover the read-only, non-destructive, open-world profile, yet the description adds substantial non-obvious behavior: a $0.1 USDC-on-Base cost, that the tool call itself is free and returns an x402 URL, and the 402 → PAYMENT-SIGNATURE → delivery handshake. It also discloses data provenance (Ni Biashara's own archive of a Bybit-derived quote) and the timestamp semantics of each point. A small deduction only because nothing is said about series length, gaps, or error behavior.

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?

Content is front-loaded — resource, window, fields, then payment mechanics — with no filler sentences. It is dense with domain and x402 jargon, but each clause carries information an agent needs.

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 output schema, the description carries the return-value burden and does so: it explains that what comes back is an x402 URL to GET rather than the data itself, and describes the payment handshake. For a one-parameter, read-only historical quote tool, nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter already documents 'USD-NGN or USD-GHS (required)'. The description repeats those values and glosses them as naira and cedi, which is mildly helpful but adds no format, casing, or default semantics beyond the schema.

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 resource (parallel street rate) with an explicit window and granularity (last 24 hours, hourly) plus the exact fields returned (mid/buy/sell, spread, depth) for USD-NGN or USD-GHS. This clearly distinguishes it from siblings get_fx_parallel (current quote) and get_fx_parallel_history_7d (longer window) without needing to open any schema.

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 24-hour window is stated, which implicitly tells an agent when this is appropriate versus the 7-day history sibling, but no alternative is named and no explicit when-not guidance is given. Usage is inferable from the title and scope rather than spelled out.

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