Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sar_nok

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden; it discloses pricing ($0.002 USDC via x402 on Base eip155:8453), the source (ECB), the possible peg-derived method, date attribution, and that the result is deterministic and non-estimated. It does not specify update cadence/freshness (e.g., daily ECB publication) or error behavior when no fixing exists.

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 sentences, front-loaded with the resource and source; the pricing tag is compact and the attributes (date, method, attribution) are enumerated tightly with no 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 parameterless single-value lookup with no output schema, the description covers source, method, date semantics, and reliability well. Missing only publication frequency/staleness and whether a cached or latest fixing is returned, which an agent may want before spending per call.

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 is 4. The description correctly leaves out parameter details and instead explains what the fixed pair means and how the rate is derived (direct, cross via EUR, or peg-derived).

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?

Specific verb+resource: 'Official SAR/NOK reference rate' with the exact source named (European Central Bank fixing) and the peg fallback. Among hundreds of fx_* siblings, this uniquely and unambiguously picks out the SAR/NOK pair.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes clear this returns a single reference rate for the SAR/NOK pair, which implicitly routes agents needing other pairs or conversions (fx_convert, fx_latest, fx_timeseries) elsewhere. It does not explicitly name those alternatives or state when not to use this (e.g., intraday/market rates), so it stops short of full guidance.

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