Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xaf_cad

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description does useful work: it discloses cost ($0.002 USDC/call), payment protocol (x402, eip155:8453), the data source, the peg fallback, and that it returns method and attribution. What it omits is update cadence and quoting convention (how many CAD per XAF), which matter for a 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?

A single dense paragraph with the paid-access header front-loaded before the purpose, and every clause (source, fallback, returned fields, no-estimate guarantee) carries information. It is slightly overpacked into one sentence, but nothing is wasted.

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 output schema, the description compensates by enumerating what comes back: rate date, method, and source attribution. What remains missing is update frequency and rate units, which an agent quoting the rate would want.

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 (both currency legs are baked into the name), so there is nothing for the description to disambiguate. The baseline of 4 applies; the description's mention of the peg fallback is a bonus rather than a parameter requirement.

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 XAF/CAD reference rate) and its provenance (latest ECB fixing, or the official peg when CAD is pegged), which is more specific than the tool name alone. Against hundreds of near-identical fx_* siblings, this tells an agent precisely which currency pair and which rate concept it is getting.

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: fetch this when you need an XAF/CAD reference rate. It never distinguishes itself from related siblings like fx_convert, fx_latest, or fx_timeseries, nor does it say when the peg-derived path applies versus the normal fixing. An agent must infer the selection rule.

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