Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xaf_ron

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

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 burden and does well: it discloses the paid access model ($0.002 USDC per call, x402, eip155:8453), the data provenance (ECB fixing), the peg fallback behaviour, and that the result is deterministic with no estimation. It does not cover error/failure behaviour or rate limits, which keeps it out of the top band.

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?

The cost/payment bracket is front-loaded, followed by purpose, method and provenance in one tight sentence. Dense but every clause adds information; only the 'Deterministic, sourced, no estimate' tail slightly overlaps the earlier provenance statement.

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 response contents: the rate, rate date, derivation method (direct, cross via EUR, or peg-derived) and source attribution. That is enough for an agent to know what it gets back for a parameterless, paid lookup.

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 baseline is 4 and no parameter explanation is required. The description does not waste words restating arguments that do not exist.

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 specific verb and resource: the official XAF/RON reference rate, with the fixing source (ECB) and the derivation method spelled out. It does not explicitly contrast itself with near-identical siblings such as fx_convert, fx_latest or fx_timeseries, but the pair-specific naming makes its scope unambiguous.

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 single-pair lookup tool rather than a bulk/convert/timeseries tool, and the stated price helps with a pay-per-call decision. There is no explicit when-to-use or when-to-prefer-a-sibling guidance, and no statement of what happens for non-pegged vs pegged RON beyond the parenthetical.

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