Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aud_aed

[PAID $0.002 USDC/call, x402, eip155:8453] Official AUD/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_aud_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 substantial work: it discloses the paid x402 model with an exact price ($0.002 USDC on eip155:8453), the authoritative source (ECB), the derivation method, and that output includes rate date and attribution. 'Deterministic, sourced, no estimate' pre-empts the natural question of interpolation or approximation. It stops short of describing failure modes or what a caller gets if no fixing exists for the day.

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 tight sentences with no filler, and every clause (price, source, method, attribution) adds distinct information. The bracketed payment preamble occupies the front-loaded position, which is defensible for a paid endpoint but delays the statement of what the tool actually does.

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?

No output schema and no parameters, so the description must convey return contents, and it does: rate, rate date, method, and source attribution. Cost and payment protocol are covered. Only stale-rate behavior and error handling are left unstated, which is a minor gap for a zero-parameter lookup.

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 for the description to disambiguate and the baseline applies. The description correctly implies a fixed currency pair requiring no caller-supplied arguments.

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?

States a specific verb+resource: 'Official AUD/AED reference rate' with the latest ECB fixing, plus the derivation method (direct, cross via EUR, peg-derived). The base/quote direction is unambiguous from the name and text, which distinguishes it from the mirror pair fx_aed_aud. It does not explicitly name any sibling as an alternative, which keeps it out of 5 territory.

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: 'latest European Central Bank fixing' signals a current-spot lookup rather than a historical series (fx_timeseries) or a conversion (fx_convert), but no alternative is named and no when-not-to-use condition is given. An agent must infer the routing decision from the rate-pair name alone.

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