Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_ron_pln

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

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?

No annotations exist, so the description carries the full burden, and it does well: it discloses the paid x402 gate ($0.002 USDC/call on eip155:8453), the data authority (ECB), the derivation method (direct, cross via EUR, or peg-derived), and that it is deterministic with no estimation. Return fields are previewed. It does not state freshness cadence (daily fixing?) or what happens on non-publishing 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?

One dense sentence that front-loads the payment requirement then the substance. Nothing is redundant; arguably the source-method enumeration could be trimmed, but it is genuinely informative rather than filler.

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, the description covers cost/auth, source authority, derivation method, and determinism, which is enough to call it correctly. What it omits is update frequency and failure modes for a paid call, which would matter to an agent budgeting spend.

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?

Zero parameters, so the baseline of 4 applies. There is nothing in the schema to clarify and the description correctly adds no parameter discussion.

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 pair: 'Official RON/PLN reference rate' with the exact source class (latest ECB fixing, or official peg when pegged). An agent knows precisely what value comes back. It does not explicitly contrast with the generic siblings fx_convert or fx_latest, which is the only gap.

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 and source rather than stated: an agent infers 'call this when you need the official RON/PLN rate'. There is no explicit when-to-use / when-not, and no pointer to fx_convert, fx_timeseries or the inverse fx_pln_ron for other needs.

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