Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_nok_czk

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description itself discloses the exact per-call charge, x402 payment mechanism and chain, latest-fixing behavior, possible calculation methods, provenance, and the no-estimate guarantee. This is unusually strong behavioral disclosure for a simple read lookup, although publication cadence and unavailable-fixing handling remain unstated.

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?

The description compactly covers payment, source, methodology, and returned metadata, with the rate's purpose immediately following the payment prefix. It is somewhat dense, and 'sourced' repeats the source-attribution point while the peg caveat appears generic for CZK.

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-argument lookup without annotations or an output schema, it provides nearly everything needed to invoke and interpret the result, including cost, rate date, method, and attribution. It could still clarify the quote convention, fixing freshness and non-publication-day behavior, and selection versus the general-purpose FX siblings.

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?

There are no parameters, so the baseline is 4 and no argument documentation is needed. The fixed pair and 'latest' wording reinforce that callers cannot supply currencies, an amount, or a date, but add little beyond the empty schema.

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?

It precisely identifies the resource as the official NOK/CZK reference rate and specifies the latest ECB fixing, rate date, calculation method, and attribution. The pair and latest/reference scope help within the large FX family, but no sibling is explicitly contrasted.

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 words 'latest,' 'official,' and 'no estimate' clearly target callers needing a current, authoritative reference fixing. It does not explicitly route amount conversions to fx_convert, historical requests to fx_timeseries, or explain its relationship to fx_latest and the reverse-pair tool.

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