Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_nzd_aed

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose useful traits: paid access ($0.002 USDC per call via x402 on eip155:8453), the underlying source, the derivation method (direct, cross via EUR, or peg-derived), and that the value is deterministic rather than estimated. It omits freshness/latency (how current the 'latest' fixing is), what happens on non-publishing days, and error or payment-failure behavior.

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 price and payment protocol, then the resource and result fields. Every clause carries information; nothing is redundant, though the bracket pricing prefix pushes the actual purpose to second position.

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?

There is no output schema, so the description must describe return content, and it does: rate, rate date, derivation method, and source attribution. Remaining gaps are quote-direction convention and data freshness cadence, which matter for a single-pair FX endpoint with no annotations or schema to fall back on.

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; there is nothing for the description to disambiguate. It does add useful meaning about what the fixed pair resolves to, though no parameter-level detail is needed or missing.

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?

Names a specific resource (the official NZD/AED reference rate) and the source (ECB fixing, or peg when pegged), which is far more than the bare pair name conveys. It does not state the quote convention (units of AED per NZD) or explicitly distinguish itself from siblings like fx_latest, fx_convert, and fx_timeseries, so routing still relies partly on the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no exclusions. With hundreds of fx_* pair siblings plus fx_latest, fx_convert and fx_timeseries, the description never says when an agent should prefer this single-pair reference endpoint over the generic latest/convert/timeseries tools.

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