Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xof_usd

[PAID $0.002 USDC/call, x402, eip155:8453] Official XOF/USD reference rate: latest European Central Bank fixing (or the official peg when USD is pegged), with the rate date, the method (direct, cross via EUR or peg-derived) and the source attribution. Deterministic, sourced, no estimate.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses the paid cost and price, the x402 payment protocol and chain (eip155:8453), the upstream source (ECB), the fallback behavior for pegged currencies, and the determinism guarantee. That is exactly the context an agent needs before spending USDC on a call.

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?

Two compact sentences: the payment/transport preamble first, then the substantive purpose with return contents. No filler, and the most decision-relevant facts (cost, source, determinism) are front-loaded.

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?

For a zero-parameter read tool with no output schema, the description effectively enumerates the returned fields (rate, rate date, method, source attribution). It stops short of stating what happens when a fixing is unavailable or how stale a rate can be, which is the only remaining gap for an agent relying on this for pricing.

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 the baseline is 4. The description correctly reinforces this by describing a fixed currency pair and 'latest' fixing, making clear there is nothing to configure.

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 names the exact resource (XOF/USD reference rate) and its provenance (official ECB fixing, or the official peg when USD is pegged), which is more specific than the bare tool name. An agent can distinguish it from the hundreds of sibling fx_* pairs without inspecting the 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?

Usage is implied rather than stated: 'Official', 'reference rate', and 'no estimate' signal this is the authoritative source versus an estimated or converted figure, and the peg fallback tells the agent coverage is guaranteed. However, no alternatives are named — fx_convert, fx_latest, or fx_timeseries are never referenced, and there is no when-not guidance.

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

All Novarithm Agent Hub: trust and commerce checks 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