Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_pln_ron

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does substantial work: it discloses the paid x402 requirement, the exact price ($0.002 USDC/call) and network (eip155:8453), the authoritative source (ECB fixing), and guarantees determinism with 'no estimate'. What it omits is update cadence and weekend/holiday behavior — an agent cannot tell how stale the 'latest' fixing might be.

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 with the payment/auth constraint front-loaded and the substantive purpose immediately after — no filler. It is slightly overpacked (price, network, source, method, determinism, return fields all in one breath), but every clause earns its place.

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?

With no output schema, the description helpfully enumerates what comes back — the rate, the rate date, the derivation method (direct, cross via EUR, or peg-derived), and source attribution — plus cost and determinism. It falls short only on freshness semantics, i.e. how often the ECB fixing refreshes and what happens on non-publishing days.

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 nothing for the description to disambiguate and the baseline of 4 applies. The description does implicitly confirm that no base/quote/date inputs are needed by fixing the pair and the 'latest' snapshot in prose.

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?

States a specific resource and scope: 'Official PLN/RON reference rate' plus 'latest European Central Bank fixing (or the official peg when RON is pegged)'. The currency pair is unambiguous, so the agent can distinguish this from the hundreds of sibling fx_<base>_<quote> tools without inspecting anything else.

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 pair-specific name and the 'reference rate' framing, but there is no explicit routing: nothing says when to prefer this over fx_convert, fx_latest, or fx_timeseries, nor any exclusion such as 'not for conversion math' or 'not intraday'. The agent must infer the choice from the tool name.

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