Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_nok_jpy

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 well: it discloses the paid prefix ($0.002 USDC/call, x402, eip155:8453), the data provenance, the peg-fallback behavior, and explicitly claims determinism and no estimation. It stops short of describing failure behavior (rate unavailable, payment rejected) or the update cadence of ECB fixings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences: the payment/billing banner is front-loaded in brackets, then the data description, with zero filler. Every clause (source, date, method, attribution, determinism) conveys distinct information.

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?

No output schema exists, and the description partly compensates by enumerating the returned fields (rate, rate date, derivation method, source attribution). The one real gap is that it never states the quote direction/number format (JPY per NOK vs the inverse), which matters for a rate tool with no schema to fall back on.

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 there is nothing to disambiguate and the baseline of 4 applies. The description correctly adds no parameter noise.

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 verb+resource: it returns the official NOK/JPY reference rate, names the authority (European Central Bank fixing) and the fallback case (official peg). The currency pair is encoded in the tool name, so no additional sibling differentiation is needed against the hundreds of fx_* pairs.

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 by the name and the phrase 'reference rate' — an agent can infer this is for a single official spot reference rather than conversion (fx_convert), a multi-pair lookup (fx_latest) or history (fx_timeseries), but the description never names those alternatives or states when not to use it. No prerequisites or freshness expectations are given beyond 'latest ECB fixing'.

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