Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aud_cny

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

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 real weight here: it discloses the paid x402 pricing model, the settlement chain (eip155:8453), the upstream source (ECB), peg fallback behavior, and that output is deterministic with no estimation. What is missing is freshness/caching policy and what happens when no fixing is available, which for a rate tool matters.

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?

It is a single dense sentence with the cost/payment metadata bracketed out front and the substantive description following, so no sentence is wasted. It is tightly packed — five separate facts in one sentence — which slightly hurts scannability but not content.

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-param lookup with no output schema and no annotations, the description pre-emptively explains the return payload (rate, rate date, derivation method, source attribution) and the data guarantee. Only edge-case behavior (stale fixing, rate unavailability, response field shape) is left unstated.

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, which is the baseline-4 case per the rubric; the currency pair is fully encoded in the tool name, so nothing further needs documenting. The description reinforces the pair and does not create ambiguity about missing arguments.

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 resource and scope: 'Official AUD/CNY reference rate' from the ECB fixing, plus how the rate is derived. An agent can distinguish this from fx_convert or fx_timeseries without opening anything, since the pair and source are named explicitly.

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 tool name and the 'reference rate' framing (this returns a single fixing, not a conversion or a series), but the description never says when to prefer it over fx_convert, fx_latest, or fx_timeseries. No exclusions or prerequisite call sequence is given.

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