Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sar_brl

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

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 load and does well: it names the payment model and price ($0.002 USDC/call, x402, eip155:8453), the data provenance (ECB fixing or official peg), the derivation method (direct, cross via EUR, peg-derived), and the fields returned (rate, rate date, method, source attribution). It does not cover failure behavior, caching, or how stale a 'latest' fixing can be, which keeps it from a 5.

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 compact sentence after the bracketed pricing tag, with the essential noun phrase ('Official SAR/BRL reference rate') up front and qualifications following. Dense but every clause carries information about source, method, or output; no filler.

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 exists, and the description compensates by enumerating the returned fields plus the method and attribution, which is exactly what an agent needs to trust the number. The remaining gap is quote convention (SAR per BRL vs BRL per SAR) and fixing freshness, both material for a rate tool.

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; the baseline applies. The one semantic detail that matters for a parameterless FX call — quote direction — is left unstated.

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 resource and scope: the official SAR/BRL reference rate, the ECB as source, and the fallback to an official peg. An agent can tell exactly which pair and which rate class it returns. It does not explicitly contrast itself with siblings like fx_convert, fx_latest or fx_timeseries, so it falls short of a 5.

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 implied rather than stated: 'Deterministic, sourced, no estimate' signals this is for authoritative reference rates rather than computed conversions, and the peg clause hints at the BRL case. There is no explicit when-to-use/when-not, and no named alternative for converting amounts (fx_convert) or fetching history (fx_timeseries).

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