Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_brl_pln

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

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 burden and does well: it discloses the paid cost ($0.002 USDC), the payment protocol and chain (x402, eip155:8453), the data provenance (ECB), the derivation method (direct, cross via EUR, peg-derived), and that results are deterministic with no estimation. It stops short of freshness details — how old the 'latest' fixing can be over weekends/holidays.

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?

Payment metadata is front-loaded in a bracketed prefix, then a single dense sentence covers source, output fields, and derivation method. Every clause earns its place, though the sentence is heavily loaded and could be split for readability.

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, but the description effectively specifies the return payload (rate, rate date, method, source attribution), which is what an agent needs. The only material gap for a no-parameter data tool is staleness/freshness guidance.

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 schema baseline of 4 applies; the description correctly offers no parameter guidance because there is nothing to configure, and the pair is fixed by the tool identity.

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?

The description names the exact resource (BRL/PLN rate), the authority behind it (European Central Bank fixing, or official peg when PLN is pegged), and what accompanies it (rate date, method, source attribution). Combined with the pair-specific tool name, an agent can tell instantly which sibling fx_* pair this covers.

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 by the pair-specific name and the 'reference rate' framing, but the description never says when to prefer this over siblings such as fx_convert, fx_latest, or fx_brl_eur cross-rates, nor does it state any precondition (e.g., that it returns only the latest fixing, not historical).

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