Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aed_ron

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 substantial work: it discloses the price and payment protocol ($0.002 USDC/call, x402, eip155:8453), the data provenance (ECB fixing), the fallback behavior (official peg when RON is pegged), the method field (direct, cross via EUR, peg-derived), and the determinism guarantee. It does not cover error behavior, staleness/caching, or what happens on non-fixing days.

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 compact sentences with no filler. The payment metadata is front-loaded, which is useful for x402-aware agents but is arguably less relevant to tool selection than the data description that follows 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 lookup with no output schema and no annotations, the description supplies what an agent needs: the source, the fallback rule, the fields returned (rate, rate date, method, source attribution), and the cost model. Remaining gaps — payment flow mechanics and error/empty-response behavior — are minor for a simple single-value read.

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 semantics to explain and the baseline of 4 applies. The description does not need to compensate for any schema gaps, and the schema is trivially complete.

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+resource combination: the official AED/RON reference rate, sourced from the latest ECB fixing or the official peg when RON is pegged. The currency pair in the name and text distinguishes it from the other fx_* pair tools. It does not, however, distinguish itself from generic siblings like fx_convert, fx_latest, or fx_timeseries, which could also return AED/RON data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no mention of alternatives such as fx_convert (for arbitrary pairs) or fx_timeseries (for historical data). Given hundreds of overlapping fx_* siblings, an explicit routing hint would be valuable and is entirely absent. The only usage-adjacent claim is 'Deterministic, sourced, no estimate', which is a quality assertion, not a selection criterion.

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