Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_hkd_cad

[PAID $0.002 USDC/call, x402, eip155:8453] Official HKD/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_hkd_cad"
  }
}

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 no annotations provided, the description carries the full burden and does well: it discloses the paid model ($0.002 USDC/call via x402 on eip155:8453), the data provenance (ECB fixing), the derivation method (direct, cross via EUR, or peg-derived), and that results are deterministic and never estimated. It also lists the components returned (rate, rate date, method, attribution), though it does not state refresh cadence or numeric precision.

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?

A single dense sentence that front-loads the paid-call notice and then the resource definition, with no filler. It is packed with clauses, so it reads as a run-on, but every clause (price, source, method, determinism) carries information an agent needs.

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?

For a zero-parameter rate lookup with no output schema, the description covers source, method, cost, determinism, and the fields returned. Remaining gaps are minor: exact refresh timing, quoting convention (units of CAD per HKD vs the reverse), and precision are not stated, which an agent may need to interpret the number correctly.

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 clarify beyond what the schema shows; the baseline for a parameterless tool applies. The description correctly avoids inventing inputs and instead spends its words on output 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?

The description names the exact resource (official HKD/CAD reference rate), the authoritative source (latest ECB fixing), and the fallback semantics (peg-derived when applicable). The currency pair in the name plus this text leaves no ambiguity about what value the tool returns, even among hundreds of fx_* siblings.

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 infers it should call this when it needs a reference HKD/CAD rate. There is no explicit statement of when to prefer it over fx_convert, fx_latest, or fx_timeseries, and no mention of staleness tolerance or when an estimate-based alternative would be acceptable.

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