Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_ron_xof

[PAID $0.002 USDC/call, x402, eip155:8453] Official RON/XOF reference rate: latest European Central Bank fixing (or the official peg when XOF 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_ron_xof"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the paid cost ($0.002 USDC/call), the x402 payment scheme and chain (eip155:8453), the upstream source (ECB), the peg fallback, and the deterministic/no-estimate guarantee. Remaining gaps are the quote direction and refresh cadence, which are not stated.

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?

A single dense sentence front-loaded with the billing/protocol tag, then the resource, source, method and guarantees. Every clause adds information, though the main sentence is long enough to read as a run-on compared with splitting source and fallback behavior.

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-argument, no-output-schema tool the description covers the important return content (rate date, method, source attribution) and the payment requirement, which is what an agent needs before spending USDC. It stops short of stating the quotation direction (RON per XOF vs XOF per RON) and how fresh the fixing is, both of which matter for correct downstream use.

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 no per-parameter meaning to add and the baseline applies. The description correctly implies the pair and source are fixed by the tool identity rather than supplied at call time.

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 and resource (the official RON/XOF reference rate), plus the exact provenance: latest ECB fixing or the official peg when XOF is pegged. That level of specificity separates it cleanly from generic siblings such as fx_convert, fx_latest and fx_timeseries 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?

Usage is only implied: 'deterministic, sourced, no estimate' signals this is the authoritative single-pair quote rather than a computed conversion, but the description never says when to prefer it over fx_convert, fx_latest or fx_timeseries, nor what to do for historical or non-ECB pairs.

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