Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_chf_aud

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 disclose the critical non-obvious traits: it is a paid call ($0.002 USDC via x402 on eip155:8453), the data is a deterministic sourced ECB fixing rather than an estimate, and the peg path is handled explicitly. What it omits is the payment mechanics an agent must actually complete (wallet/balance requirement, failure or 402 behavior) and the freshness cadence of the ECB fixing.

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 with no filler, front-loaded with the cost/payment tag an agent needs before deciding to spend, then the substantive rate description. The run-on construction packs a lot into one line but every clause (source, peg fallback, date, method, attribution, determinism) adds information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must convey the return shape, and it does list rate date, method and attribution. However, it never states the quoting direction/units (AUD per CHF vs CHF per AUD) or how stale the fixing can be, both of which matter for an FX rate and are neither in the empty schema nor in annotations.

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; there is nothing for the description to disambiguate. The description correctly implies the pair and source are baked into the tool rather than supplied by the caller.

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 (CHF/AUD) and the exact authority behind it (the latest European Central Bank fixing), plus what accompanies the number (rate date, derivation method, source attribution). Against ~600 sibling FX pairs plus fx_convert/fx_latest/fx_timeseries, the pair and the ECB-sourced single-fixing scope make it unambiguous which tool this is.

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: it is clearly a single-pair, latest-fixing lookup, and the 'no estimate' phrasing hints it should be preferred when an auditable official rate is needed. But it never states when to use this versus fx_convert (conversion math), fx_latest (multi-pair snapshot) or fx_timeseries (history), nor does it mention any prerequisite such as holding USDC on Base.

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