Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_jpy_ron

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations present, the description carries the full disclosure burden and does so well: it states the price and payment rail ('$0.002 USDC/call, x402, eip155:8453'), the freshness rule (latest ECB fixing), the pegged-currency fallback, the resolution method, and that the value is deterministic and sourced rather than estimated. This tells the agent about cost, provenance and edge-case behavior before it decides to call.

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?

It is a single tightly packed sentence with no filler, and the substantive facts (source, fallback, method, attribution) all earn their place. The one structural weakness is front-loading the bracketed payment/rail metadata ahead of the actual purpose, which delays the agent's recognition of what the tool returns.

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-param tool with no output schema and no annotations, the description covers price, source, freshness, fallback logic and returned fields (rate date, method, source attribution), which is close to complete. The remaining ambiguity is the quote direction of 'JPY/RON' (RON per JPY vs JPY per RON) and the numeric format, which are not resolved anywhere.

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 no parameters, so there is no parameter semantics to add; the 0-param baseline applies. Nothing in the description contradicts or muddies the empty schema.

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 a specific verb+resource pair — the 'official JPY/RON reference rate' — and immediately pins the source and vintage: 'latest European Central Bank fixing (or the official peg when RON is pegged)'. That separates it from generic conversion/list siblings such as fx_convert, fx_latest and fx_timeseries without requiring the schema to be opened.

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: the agent can infer this is the single-pair spot reference rate for JPY/RON, and 'no estimate' hints it should be preferred over modelled rates. But there is no explicit when-to-use or when-not-to-use, and no named alternative (fx_convert for amount conversion, fx_timeseries for history) is called out.

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