Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_jpy_brl

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the payment requirement ($0.002 USDC/call, x402, eip155:8453), the data provenance, and the determinism guarantee — meaningful context beyond the schema. However, it omits the return shape/numeric conventions, what happens on non-fixing days, and any error or rate-limit behavior, and it does not say whether it is read-only.

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 tight sentences with no filler, but the payment metadata is front-loaded ahead of what the tool actually returns, delaying the most decision-relevant content by a clause. Slight restructuring would improve it; nothing is redundant.

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, no-output-schema tool this is largely sufficient: fields returned (rate date, method, attribution) are enumerated and the fallback-to-peg case is covered. The main gap is the absence of any statement about freshness cadence or how stale the 'latest' fixing can be.

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 to disambiguate and the baseline is 4. The description correctly implies the pair is fixed by the tool name rather than parameterized.

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 resource (the official JPY/BRL reference rate), names the exact source (latest ECB fixing or official peg), and describes the derivation (direct, cross via EUR, peg-derived). An agent can distinguish it from the many sibling fx_* pairs — including the inverse fx_brl_jpy — without opening a schema.

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?

The description implies when this is appropriate (official/reference-rate needs, with 'no estimate'), but never names alternatives such as fx_latest, fx_convert, or fx_timeseries, nor says when a different pair or a conversion tool should be preferred. Usage is inferable from the pair name but not guided.

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