Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_inr_nok

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 load and does well: it discloses the paid x402 model ($0.002 USDC/call on eip155:8453), the data provenance (ECB fixing, peg fallback for NOK), and the determinism guarantee ("no estimate"). It stops short of explaining the payment handshake, update cadence, or failure behavior for non-trading days.

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, front-loaded with the cost/payment tag and then the core purpose, provenance and return contents. "Deterministic, sourced, no estimate" is terse and earns its place as a trust signal rather than padding.

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-param tool with no output schema and no annotations, the description covers the essentials: what the rate is, where it comes from, and which fields come back (rate date, derivation method, source attribution). Missing only the response envelope shape and freshness cadence, which are minor for a reference-rate lookup.

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 schema surface for the description to compensate for; baseline 4 applies. The description correctly implies the pair and source are baked into the endpoint rather than parameterized.

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?

The description states a specific resource ("Official INR/NOK reference rate") with a named source ("latest European Central Bank fixing"), which is enough to distinguish it from the other ~500 fx_* pair tools by currency. It does not clarify quote direction (INR-per-NOK vs NOK-per-INR), which is the one thing an agent could get wrong when choosing between this and fx_nok_inr.

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: fetch this when you need the INR/NOK reference rate. There is no explicit when-to-use/when-not, and no routing to relevant siblings such as fx_convert (for actual conversion), fx_timeseries (for historical series) or fx_latest (for a multi-pair snapshot).

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