Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_nzd_xof

[PAID $0.002 USDC/call, x402, eip155:8453] Official NZD/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_nzd_xof"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 well: it discloses the payment model and network (x402, eip155:8453), the data provenance (ECB fixing, official peg when XOF is pegged), the derivation method (direct, cross via EUR, peg-derived) and asserts determinism with no estimation. What it omits is availability/freshness behavior (publishing cadence, weekend/holiday staleness) and error behavior for a paid call.

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?

Two compact sentences, front-loaded with the price/transport tag and immediately followed by what the rate is and where it comes from. The trailing fragment 'Deterministic, sourced, no estimate.' is terse but earns its place as a trust signal. No filler.

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, no-output-schema lookup tool this covers what an agent needs: the quoted pair, the source, the fallback for a pegged currency, and the components returned (rate date, method, attribution). Missing only freshness/publishing-cadence notes that would matter for a paid, single-value call.

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 requires no parameter explanation and instead spends its words on provenance and output composition.

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 specific verb and resource: 'Official NZD/XOF reference rate: latest European Central Bank fixing' with the peg fallback named. The pair and source are unambiguous. It stops short of differentiating itself from siblings like fx_latest, fx_convert or fx_timeseries, which the agent must infer from the pair name alone.

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 by the pair-specific name and the phrase 'reference rate' (not a conversion), but there is no explicit when-to-use guidance and no pointer to alternatives such as fx_convert for arithmetic or fx_timeseries for history. The only explicit guidance is pricing-related ($0.002 USDC/call, x402).

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