Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_nok_ron

[PAID $0.002 USDC/call, x402, eip155:8453] Official NOK/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_nok_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 behavioral burden and does so well: it discloses the price ($0.002 USDC/call), the payment protocol and network (x402, eip155:8453), the authoritative data source (ECB), the derivation method (direct, cross via EUR, peg-derived), and that results are deterministic with no estimation. It does not cover failure modes, staleness handling, or caching, which keeps it from a 5.

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?

Effectively two sentences with the payment/cost note front-loaded in brackets, followed by the substance. Nearly every clause carries information; the only slight redundancy is restating 'sourced' alongside the ECB attribution and source attribution phrase.

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, single-value tool with no output schema, the description supplies source, methodology, determinism, cost and payment mechanics. The main residual gap is return shape and error behavior (e.g. what happens when no fixing exists for a date), which the absent output schema leaves undocumented.

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 correctly spends its space on output context (rate date, method, attribution) instead of inventing inputs.

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 specific resource and scope: the official NOK/RON reference rate, sourced to the ECB fixing or an official peg. It also says what comes back (rate date, derivation method, source attribution), so the operation is unmistakable. It stops short of distinguishing itself from the many sibling pair tools (e.g. fx_convert, fx_latest, fx_timeseries) by name.

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 explicit when-to-use or when-not-to-use guidance, and no routing to alternatives among the hundreds of fx_* siblings. Usage is only implied by the phrase 'Official NOK/RON reference rate', which suggests reference/official-rate use versus conversion, but an agent must infer that.

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