Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_gbp_nok

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the per-call price and payment protocol (x402, eip155:8453), the upstream source (ECB), the derivation method (direct, cross via EUR, or peg-derived), and that results are deterministic rather than modelled. It stops short of describing freshness cadence, rate-limit behaviour, or what happens on non-fixing days.

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?

Tight and front-loaded, with the payment tag bracketed so it does not bury the purpose. A few clauses ('or the official peg when NOK is pegged') add genuine information rather than filler, though the sentence runs long before reaching 'Deterministic, sourced, no estimate'.

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 and no parameters, so the description must supply return semantics, and it does: rate, rate date, method, and source attribution are all enumerated. The main omission is temporal detail — how current the fixing is and how pegged regimes are surfaced — which matters for a 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?

Zero parameters, so there is nothing to disambiguate and the baseline applies. The description instead documents the shape of the result — rate date, method, source attribution — which is the useful substitute when the schema is empty.

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 pair — 'Official GBP/NOK reference rate' — and pins the source as the latest ECB fixing, with the peg fallback named. The currency pair in the name is resolved unambiguously and the flavour of rate (official reference, not market mid) is settled immediately.

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?

Implied usage is present: 'deterministic, sourced, no estimate' signals this is the right choice when an auditable official fixing is needed rather than a converted or estimated number. But no sibling is named — fx_convert, fx_latest and fx_timeseries exist and the description never says when to prefer this pair-specific endpoint over them.

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