Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cny_mxn

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 paid model ($0.002 USDC/call via x402 on eip155:8453), the source (ECB), the peg fallback, and the determinism guarantee ('no estimate'). It does not state what happens when no fixing is available, error behavior, or how stale the 'latest' fixing can be (weekend/holiday gaps).

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?

Two dense sentences with the cost/payment banner front-loaded, followed by the substantive purpose. Every clause adds information (source, fallback, returned fields, determinism); nothing is redundant.

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?

Because there is no output schema, the description usefully enumerates what comes back: the rate, the rate date, the derivation method (direct, cross via EUR, or peg-derived), and source attribution. It omits failure/empty-result semantics and freshness cutoffs, which are the remaining gaps for a data-lookup 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 the baseline is 4 and there is nothing for the description to disambiguate. The description correctly signals that the call is argument-free by describing a fixed currency pair.

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 the exact resource and scope: 'Official CNY/MXN reference rate: latest European Central Bank fixing (or the official peg when MXN is pegged)'. That is a specific verb+resource and makes the data provenance unambiguous. It stops short of explicitly contrasting with siblings like fx_convert, fx_latest or fx_timeseries, relying on the pair-encoded tool name for differentiation.

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: an agent can infer this is the right call when it needs the official ECB reference fixing for the CNY/MXN pair. There is no explicit 'use this instead of fx_convert/fx_latest when...' statement and no when-not guidance, which matters in a sibling set containing hundreds of fx_* pairs plus a generic converter.

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