Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xof_cny

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 behavioral burden and does well: it discloses a paid x402 call at $0.002 USDC on eip155:8453, the underlying data source (ECB fixing), the fallback path when CNY is pegged, and the derivation method (direct, cross via EUR, peg-derived). It stops short of describing failure/availability behavior or caching, which keeps it below a 5.

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?

Three compact clauses: payment terms, then the resource, then the returned attributes and the determinism guarantee. No filler, and the cost/protocol notice is front-loaded so an agent sees the paid nature before deciding to call.

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 everything an agent needs: what is returned (rate, rate date, method, source attribution), where it comes from, and that the call costs USDC. Only the payment mechanics (how the x402 challenge is satisfied) are left implicit, which is a minor gap for a paid tool.

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 nothing for the description to disambiguate and the baseline of 4 applies. The pair is encoded in the tool name, making the empty schema unambiguous.

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 a specific resource (the official XOF/CNY reference rate) and its provenance (latest ECB fixing, or peg when CNY is pegged), which fully disambiguates it from the many other fx_* pair tools. The verb/resource combination is concrete and an agent can tell exactly what it returns without reading anything else.

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: 'reference rate', 'deterministic, sourced, no estimate' signals this is for an official benchmark rather than a market/estimated quote, which helps steer an agent away from estimation-style siblings. However, it never names an alternative (e.g. fx_convert for conversion math or fx_timeseries for history) or states when this pair tool should be preferred over a cross via another pair.

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