Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_hkd_nok

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does substantial work: it discloses the payment model and price ($0.002 USDC/call via x402 on eip155:8453), the authoritative source (ECB), the fallback logic (official peg when NOK is pegged), the derivation method (direct, cross via EUR, or peg-derived), and the determinism guarantee with no estimation. It omits failure/error behavior and whether the rate can lag a publication calendar, which keeps it below a 5.

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 cost/payment tag up front, then one dense sentence covering source, fallback, method, and returned fields. No filler, and the most decision-relevant facts (cost, official source) are front-loaded.

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?

With no annotations and no output schema, the description must self-document, and it names the returned elements (rate, rate date, method, source attribution) so the agent knows what to expect. It does not state quote direction (whether 1 HKD = X NOK) or the expected magnitude/format of the rate, a minor but real gap for a zero-argument FX tool.

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 the schema has nothing to explain and the baseline of 4 applies. The description correctly implies the call is fully determined by the tool name, with no dates or options to supply.

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 (HKD/NOK reference rate) with a precise qualifier (latest ECB fixing, or official peg when NOK is pegged) and the specific subfields returned. Among hundreds of near-identical fx_* siblings, the currency pair is unambiguous in the name and reinforced by the description.

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?

The description implies when this is the right call (you want the official reference fixing for HKD/NOK, not an estimate), but it never names alternatives such as fx_convert for conversion arithmetic, fx_latest for a general latest-rate lookup, or fx_timeseries for historical series. The agent must infer routing from sibling names alone.

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