Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_nok_cve

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

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?

With no annotations, the description carries the behavioral burden and does reasonably well: it discloses the commercial terms ($0.002 USDC/call, x402, eip155:8453), the authoritative source (ECB), the peg fallback path, and that output is deterministic and not estimated. It omits failure/payment-failure behavior and any staleness or error handling, which keeps it below 5.

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?

Two compact clauses: the bracketed payment/transport metadata first, then the data description. Both earn their place, and the core identification ('Official NOK/CVE reference rate') arrives early. The payment bracket is slightly noisy at the front but is genuinely decision-relevant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, no annotations, and no output schema, the description must supply everything an agent needs, and it does: what the number is, where it comes from, what fallback applies, what metadata accompanies it (rate date, method, attribution), and what it costs. Little of operational relevance is missing.

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 nothing for the description to disambiguate; the baseline of 4 applies. The description instead spends its words on the return semantics, which is the right allocation for a parameterless tool.

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 pair ('Official NOK/CVE reference rate') plus the concrete source ('latest European Central Bank fixing') and a defined fallback ('the official peg when CVE is pegged'). An agent can distinguish this from the parameterized siblings (fx_latest, fx_convert, fx_timeseries) purely from the description, since this tool is hard-wired to one currency pair.

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?

Implicitly defines its use case: fetch the single latest NOK/CVE reference fixing. It never explicitly says when to prefer it over fx_latest, fx_timeseries (historical) or fx_convert (arithmetic conversion), so the routing decision is left to inference from the tool name and pair specificity.

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