Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cny_nzd

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

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 price and payment mechanism ($0.002 USDC, x402, eip155:8453), guarantees determinism ('no estimate'), names the upstream source (ECB fixing) and the derivation method (direct, cross via EUR, peg-derived), and explains the peg fallback. It stops short of saying how stale the fixing can be or rate-limit behavior.

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 with the paid-endpoint metadata bracketed up front, followed by the substance. Every clause earns its place, though the appended 'Deterministic, sourced, no estimate' is slightly redundant with 'Official ... reference rate'.

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?

No output schema exists, so the description needs to indicate what comes back – it does, listing the rate date, derivation method, and source attribution alongside the rate itself. Only freshness/latency of the fixing and error behavior are absent.

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; there is no parameter meaning to convey and the description correctly implies the call is argument-free.

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 resource – the official CNY/NZD reference rate from the ECB fixing – with the scope (latest fixing, or peg when NZD is pegged). The currency pair is only implied by the tool name, so the description does not explicitly say how it differs from the hundreds of sibling fx_* pair tools or from fx_convert/fx_latest, but the resource itself is unambiguous.

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 (call this when you need a CNY/NZD reference rate), and the peg fallback describes what happens rather than when to prefer this tool. It never mentions fx_convert, fx_latest, or fx_timeseries as alternatives for other pairs, conversions, or history, leaving routing to inference from the tool name.

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