Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xaf_cny

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full disclosure burden, and it does substantial work: it discloses the paid model ($0.002 USDC/call, x402, eip155:8453), the authoritative source (ECB fixing or official peg), the derivation method (direct, cross via EUR, peg-derived), and guarantees determinism with no estimates. It does not address weekend/holiday staleness, error behavior, or what a refusal looks like, which are real gaps for a rate tool.

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 with no filler, and the provenance and determinism claims are front-loaded. The bracketed payment prefix ($0.002 USDC/call, x402, eip155:8453) is dense but earns its place by warning the agent this call costs money before it invokes it.

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-annotation, no-output-schema tool this is close to sufficient: source, method, rate date, and attribution are all described, effectively previewing the return payload. Only the exact response shape and stale-data handling remain unspecified.

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; the baseline for a parameterless tool applies. It does not need to compensate for any schema gap here.

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 a specific resource and scope: 'Official XAF/CNY reference rate' tied to the 'latest European Central Bank fixing.' That is far more precise than the bare pair name. It stops short of differentiating from the many siblings that also return rates (fx_latest, fx_convert, fx_timeseries), so an agent must infer the distinction from the pair code 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 only implied: the agent can infer 'call this when you need the XAF/CNY reference rate.' There is no explicit when-to-use versus when-not, and no routing to fx_convert for conversion or fx_latest for multi-pair retrieval, which matters given hundreds of near-identical siblings.

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