Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_ron_eur

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does well on the commercial and provenance side: it discloses the $0.002 USDC x402 price, the chain (eip155:8453), the ECB source, the peg fallback, and that the result is deterministic and not an estimate. It omits operational behavior an agent needs: update cadence/staleness of the fixing, what happens on weekends or bank holidays, and failure modes when no fixing is published.

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?

A single dense sentence preceded by a bracketed pricing/payment tag; nothing is padded. The pricing prefix is front-loaded, which is the right call for an agent that must budget calls. Slightly heavy with parentheticals, but every clause carries information.

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 naming the returned fields: rate, rate date, method (direct, cross, or peg-derived), and source attribution. For a 0-param fetch tool that is close to complete. The remaining gap is freshness cadence and error behavior, which an agent cannot derive from the schema.

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 no parameter meaning for the description to add. Baseline for a 0-param tool applies.

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 precise verb+resource: the official RON/EUR reference rate from the latest ECB fixing, with the peg fallback spelled out. The currency pair in the tool name is confirmed and the direction of quotation is unambiguous. It stops short of naming the near-duplicate siblings (fx_eur_ron for the inverse, fx_convert for amount conversion), so differentiation is inferred rather than stated.

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 single-purpose nature of a zero-argument rate fetcher, but there is no explicit when-to-use or when-not guidance. It never says to prefer fx_convert when converting an amount, or fx_eur_ron when the inverse quote is needed, which matters given hundreds of near-identical sibling tools.

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