Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cny_kmf

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

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 supplied, the description carries the full burden and does well: it discloses the cost and payment mechanism ('$0.002 USDC/call, x402, eip155:8453'), the upstream source (ECB), the derivation method (direct, cross via EUR, or peg-derived), and the deterministic no-estimate property. It stops short of describing error behavior or staleness handling, but the economically relevant traits are surfaced.

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?

Content is front-loaded in one dense sentence after a bracketed payment tag; every clause (source, method, date, attribution, determinism) adds information. The bracketed pricing preamble is slightly noisy relative to the substantive text but is legitimately useful for a paid x402 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?

The description compensates for the absence of an output schema by enumerating the returned fields (rate date, derivation method, source attribution). The main residual gap is quote convention — whether the value is CNY-per-KMF or KMF-per-CNY — which is only resolved by the naming convention shared with sibling fx tools.

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; the description confirms the instrument is fully determined by the tool name (a fixed pair with a fixed source). Nothing further is needed from a parameter standpoint.

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 ('Official CNY/KMF reference rate') and specific content ('latest European Central Bank fixing'), so the verb+resource is unambiguous. It does not explicitly distinguish itself from siblings such as fx_convert, fx_latest, or fx_timeseries, leaving the agent to infer differentiation from 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?

Usage is implied rather than stated: 'latest ECB fixing' signals a point-in-time spot lookup for this specific pair, and 'no estimate' signals authoritative data. There is no explicit statement about when to prefer fx_convert for arbitrary pairs, fx_timeseries for history, or what to do when a fixing is unavailable, so an agent must infer the boundary among hundreds of fx 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