Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cny_xof

[PAID $0.002 USDC/call, x402, eip155:8453] Official CNY/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_cny_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 supplied, the description carries the full load and does well: it discloses the $0.002 USDC cost, the x402 payment protocol, the chain (eip155:8453), the data source, and a fallback path (peg-derived) when no ECB fixing exists. It does not disclose freshness behavior on non-fixing days, weekend/holiday handling, or response shape, which leaves residual gaps for a priced read.

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?

One front-loaded sentence with the payment metadata bracketed up front, then purpose, provenance and method. It is dense but every clause (rate date, method, attribution, no-estimate) conveys something an agent could act on.

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, the description covers source, contributing metadata fields (rate date, method, attribution) and reliability guarantees. Missing only tie-break guidance versus the many sibling fx tools and any note on data freshness cadence.

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-argument meaning to add and the description correctly does not invent any. The pair and source are fully encoded in the tool identity, making further parameter discussion unnecessary.

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?

The description names the exact resource ('Official CNY/XOF reference rate') and origin ('latest European Central Bank fixing'), which separates it from the bulk of the fx_* siblings that differ only by currency pair. It stops short of naming a functional alternative such as fx_convert or fx_latest, so the differentiation is by pair and source rather than by use case.

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 paid-call notice and 'no estimate' framing imply this is the authoritative lookup for this pair, but there is no explicit when-to-use or when-not guidance against siblings like fx_convert, fx_latest or fx_timeseries. The peg fallback ('or the official peg when XOF is pegged') is the only conditional behavior described.

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