Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_nok_chf

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the payment requirement (paid, $0.002 USDC via x402 on eip155:8453), the data provenance (ECB fixing, official peg fallback when CHF is pegged), the determinism guarantee ('no estimate'), and the method used (direct, cross via EUR, or peg-derived). These are exactly the behavioral facts an agent needs before spending money on a call.

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 compact clauses: a bracketed payment/transport tag, then the purpose with provenance and guarantees. Every phrase carries information (source, vintage, fallback, method, determinism) and the purpose is front-loaded after the billing tag.

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, no-output-schema tool this is nearly complete — it covers cost, source, cadence (latest fixing), and returned fields. The one material omission is quote direction/convention (NOK per CHF vs CHF per NOK) and numeric precision, which matters for an FX consumer.

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 goes slightly further by enumerating what the response carries — rate date, method, source attribution — which substitutes for the absent output schema.

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 resource and verb-equivalent: 'Official NOK/CHF reference rate: latest European Central Bank fixing.' The currency pair, the issuing authority (ECB), and the fixing vintage are all named, so an agent can distinguish this from the ~700 other fx_* pair tools without opening the schema.

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 rather than stated — you use it when you want the official NOK/CHF reference rate. There is no explicit routing guidance against the obvious alternatives in the sibling set (fx_convert, fx_latest, fx_timeseries) and no statement of when this is the wrong choice, e.g. for intraday or historical quotes.

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