Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aud_xaf

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does real work here: it discloses the cost ($0.002 USDC/call via x402 on eip155:8453), the authoritative source (ECB fixing), the derivation method (direct, cross via EUR, or peg-derived), and that values are deterministic with no estimation. What is left unsaid is the exact quote convention (units of quote per base) and whether a cached/stale fixing is possible.

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?

Two sentences, front-loaded with the payment/transport metadata the caller needs before invoking and then the rate semantics. The bracket prefix adds slight noise but is legitimately conditional information an agent must see before paying.

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

Completeness5/5

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

For a zero-parameter, no-annotations pricing tool, the description covers the missing pieces an agent actually needs: cost and payment protocol, data source, determinism guarantee, and the fields returned (rate date, method, attribution). Little in the calling contract is left unknown.

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?

Zero input parameters, so the baseline of 4 applies; there is no parameter meaning for the description to compensate for, and the pair is encoded in the tool name.

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 and scope: 'Official AUD/XAF reference rate: latest European Central Bank fixing (or the official peg when XAF is pegged)'. The currency pair and source are unambiguous, and it implicitly distinguishes itself from siblings like fx_convert or fx_latest, which are generic rather than pair-specific.

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 by the pair-specific name and the 'reference rate' framing, but there is no explicit when-to-use guidance: nothing says whether to prefer fx_convert for amounts, fx_latest for the newest snapshot, or fx_timeseries for history. The peg-vs-fixing fallback is a behavioral note, not routing guidance.

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