Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aed_aud

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 the x402 payment requirement ($0.002 USDC per call on eip155:8453), the upstream source (ECB), and the fallback behavior when AUD is pegged. It stops short of describing error behavior, caching/freshness limits beyond 'latest fixing', or what happens if payment is missing.

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 payment terms, then the rate definition, then the return metadata. Every clause carries information, though the bracketed pricing prefix slightly obscures the primary purpose for a reader scanning for what the tool does.

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-output-schema tool this is complete: it names the returned fields (rate date, derivation method, source attribution) and states the determinism guarantee. An agent knows both what it will get and what it will cost before calling.

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 and there is nothing for the description to disambiguate. The description correctly avoids restating a schema that does not exist.

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 states a specific resource and scope: the official AED/AUD reference rate from the ECB fixing, plus the peg fallback. It is clearly distinguishable from non-FX siblings, but it does not disambiguate direction against the inverse sibling fx_aud_aed or clarify how it relates to fx_convert/fx_latest.

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 via 'no estimate' and 'official ... reference rate', which suggests it is the right pick when a sourced, auditable fixing is needed rather than a computed conversion. It never names alternatives such as fx_convert for cross-rate math or fx_timeseries for history, and gives no when-not guidance in a family of hundreds of near-identical siblings.

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