Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cny_hkd

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden, but it does useful work: it discloses the payment requirement and price ($0.002 USDC/call via x402 on eip155:8453), the upstream source (ECB), the peg fallback, and that the result is deterministic and non-estimated. It still omits update cadence, failure behavior when no fixing exists, and whether the rate is quoted as CNY per HKD or the inverse.

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?

Front-loaded with the core purpose, with the payment metadata bracketed up front so an agent knows the cost before committing. It is dense but every clause (source, date, method, attribution, determinism) adds information; the only mild redundancy is 'sourced' alongside 'source attribution'.

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?

With no parameters, no annotations, and no output schema, the description supplies the provenance, cost, and determinism guarantees an agent needs. The remaining gap is quote convention and data freshness, which matter for a rate lookup but are secondary for a single-value call.

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 of 4 applies. The description correctly adds no parameter guidance and instead spends its words on provenance.

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 resource (CNY/HKD reference rate) with an explicit verb-like framing and names the authoritative source (latest ECB fixing) plus the fallback case (official peg when HKD is pegged). An agent can distinguish it from the hundreds of sibling fx_* pair tools purely from the name and this sentence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives such as fx_convert or fx_latest for conversion versus raw-rate retrieval. Usage is only implied by the tool name and the 'latest ECB fixing' phrasing.

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