Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cny_eur

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

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 zero annotations the description carries the full burden, and it does substantial work: it discloses per-call pricing ($0.002 USDC via x402 on eip155:8453), the upstream source (ECB fixing), the peg fallback for pegged periods, and that the result is deterministic with no estimation. Missing is the publication cadence/rate freshness (e.g. no weekend or holiday fixings) and what happens on failure, which matters for a paid rate lookup.

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?

One dense sentence plus a bracketed payment tag; nothing is padded and the substantive claim (official ECB fixing) follows immediately. The leading bracketed cost/chain metadata is noisy for an agent scanning many siblings, but it is genuinely necessary context for a paid endpoint.

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?

There is no output schema and no input schema, so the description must describe the return: it names the rate, the rate date, the derivation method (direct, cross via EUR, peg-derived), and source attribution, which is enough to interpret a response. The remaining gap is temporal behavior, i.e. how stale the 'latest' fixing can be.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description instead spends its words on output content (rate date, method, source attribution), which is useful but sits outside parameter semantics.

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 verb+resource: 'Official CNY/EUR reference rate: latest European Central Bank fixing.' The pair direction is unambiguous, and 'official ... reference rate' plus the named source separates it from the hundreds of sibling fx_* pair tools that use the same naming pattern.

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 rather than stated: 'Deterministic, sourced, no estimate' signals this is the authoritative-reference choice over estimated data sources, and the fixed pair implies an agent wanting the inverse should pick fx_eur_cny. However, no sibling (fx_convert, fx_latest, fx_timeseries) is named and no when-not guidance 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