Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aud_brl

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description discloses important behavior directly: a paid $0.002 USDC call, x402 payment, and the eip155:8453 network. It also explains the ECB source, possible direct/cross/peg-derived methods, determinism, absence of estimation, and inclusion of the rate date and source attribution.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The payment details are compact and front-loaded, followed by two dense sentences covering purpose, freshness, methodology, provenance, and determinism. Nearly every phrase supports tool selection, payment handling, or result interpretation, with minimal boilerplate or redundancy.

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 simple zero-input lookup without an output schema, the description supplies the essential invocation and result context: currency pair, latest-reference semantics, source, rate date, derivation method, attribution, and call cost. Explicit sibling routing would improve selection further, but its absence does not impede correct invocation or interpretation.

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 has zero parameters, so the no-parameter baseline of 4 applies and there are no undocumented arguments requiring explanation. Fixing both currencies and the latest-rate scope in the description makes the empty invocation unambiguous.

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 identifies the exact resource and scope: an official, latest AUD/BRL reference rate based on the European Central Bank fixing. The pair-specific name separates it from other fx_* pair tools, but the description does not explicitly distinguish its role from fx_latest, fx_convert, or fx_timeseries.

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

Usage Guidelines4/5

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

The terms "Official," "latest," and "no estimate" provide clear context for choosing this tool when an authoritative current reference rate is needed. It gives no explicit when-not guidance or sibling routing for currency conversion, historical series, or other latest-rate requirements.

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