Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_brl_xof

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

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 load and does well: it discloses the paid x402 cost and chain (eip155:8453), the upstream source (ECB), the derivation method returned (direct, cross via EUR, or peg-derived), and guarantees determinism with no estimation. It does not mention error behavior when a fixing is unavailable or how stale a fixing may be.

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 sentences, front-loaded with the payment tag and then the substance; every clause (source, peg fallback, method, attribution) adds information. The bracketed payment prefix is dense but carries real cost/transport information the agent needs before calling.

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?

For a zero-parameter, output-schema-less rate lookup the description enumerates what comes back (rate, rate date, method, source attribution) and how the value is derived, which is nearly everything needed. A note on unavailability or freshness of the fixing is the only material gap.

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?

Zero input parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description instead spends its words on output semantics, which is the right trade-off for a fixed-pair tool.

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 names a concrete resource ('Official BRL/XOF reference rate') and specifies the source (latest ECB fixing) plus the fallback case (official peg when XOF is pegged). The pair is unambiguous and the sibling set is disambiguated by the tool name itself, so no further differentiation is needed, though the text never explicitly contrasts itself with fx_latest, fx_timeseries or fx_convert.

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: an agent can infer this is the point-in-time lookup for one fixed pair, and 'no estimate' signals when not to rely on it. But there is no statement of when to prefer fx_convert (conversion), fx_timeseries (historical series) or fx_latest, and no prerequisites beyond the embedded price tag.

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