Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cny_cad

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

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 cost ($0.002 USDC/call), the x402 payment protocol and network (eip155:8453), the underlying source (ECB fixing, or official peg), and that results are deterministic and sourced rather than estimated. Gaps remain around error/failure behavior when payment is absent and whether any rate staleness handling applies.

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 sentences, front-loaded with the payment tag and then the core resource definition; every clause adds information. The bracketed payment prefix is dense but placed first, so it does not bury the purpose.

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 annotations or output schema exist, so the description must convey behavior itself, and it covers sourcing, method (direct/cross via EUR/peg-derived), rate date, and attribution. It stops short of describing the response shape or value formatting, which would be useful given the absent output schema.

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; baseline applies. The description correctly signals a parameterless call by naming the pair implicitly through the tool name.

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 concrete verb-plus-resource: 'Official CNY/CAD reference rate: latest European Central Bank fixing', which is unambiguous about the currency pair and data source. It does not name or rule out sibling tools such as fx_convert, fx_latest, or fx_timeseries, so differentiation relies on the pair encoded in the name.

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?

Implied usage is clear enough (fetch a reference fixing for CNY/CAD), and 'no estimate' hints that it is unsuitable for derived or forecast values. However, there is no explicit when-to-use/when-not guidance and no pointer to fx_convert for actual conversions, fx_timeseries for historical series, or fx_latest for a general latest-rate lookup.

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