Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aed_brl

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 paid x402 flow, the $0.002 USDC price, the chain (eip155:8453), the authoritative source, the peg fallback behavior, and that the result is deterministic and non-estimated. It leaves out what happens when no ECB fixing exists for a date (weekends/holidays) and any error 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?

One dense sentence plus a bracketed payment tag, with no wasted clauses. Minor weakness: the price/protocol tag leads the string, pushing the actual purpose to second position when it should be front-loaded.

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 annotations, so the description must describe the return payload, and it does: rate date, derivation method (direct, cross via EUR, peg-derived), and source attribution. For a zero-parameter lookup this is essentially complete; only holiday/publication-gap behavior is missing.

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 beyond the schema to explain; baseline is 4. The description correctly adds no phantom inputs and instead spends its words on source, fallback, and payment, which is the right trade for a parameterless call.

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 verb and resource: it returns the official AED/BRL reference rate, and names the exact source (latest ECB fixing) plus the peg fallback. Against a sibling list of hundreds of near-identical fx_<base>_<quote> tools, the name plus description pin down the pair unambiguously.

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?

Implicit usage guidance is present: 'official ... reference rate' and 'no estimate' signal this is for authoritative reference data rather than approximate conversions, and the x402 payment line signals the cost precondition. However, it never names alternatives such as fx_convert, fx_latest or fx_timeseries, nor states when a caller should prefer one over this.

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