Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cad_aed

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

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, the description carries the full burden and does well: it discloses a per-call price ($0.002 USDC), the x402 payment scheme and chain (eip155:8453), the data provenance and that results are deterministic rather than estimated. It still omits failure behavior (unknown/unsupported pair, stale fixing, payment rejection) and any rate-limit policy beyond the per-call charge.

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?

The payment/billing tag is front-loaded and the substantive content follows in one dense sentence; every clause carries information. The closing 'Deterministic, sourced, no estimate' partially restates 'official ... reference rate' and could be trimmed.

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 lookup this is nearly complete: source, datedness, derivation method, attribution and cost are all stated even though there is no output schema. It could go one step further by naming the response format or freshness cadence of the ECB fixing.

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 to disambiguate and the baseline of 4 applies. The description adds useful semantics about what a call yields (rate, date, method, source) without needing parameter detail.

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 the exact resource (CAD/AED reference rate), its source (European Central Bank fixing, or the official AED peg) and the fields returned (rate date, derivation method, attribution). That is far more specific than the tool name alone. It does not explicitly contrast itself with siblings such as fx_convert or fx_latest, so it stops short of a 5.

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: 'reference rate' and 'no estimate' signal this is for official/audit-grade figures rather than ad-hoc conversion, and the paid-call tag warns of cost. There is no explicit when-not clause and no pointer to alternatives like fx_convert for converted amounts or fx_latest for cross-pair lookups.

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