Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_eur_isk

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses cost ($0.002 USDC per call via x402 on eip155:8453), the authoritative source (ECB fixing), the derivation method (direct, cross via EUR, or peg-derived), and guarantees determinism with no estimation. It does not cover weekend/holiday staleness, caching, or failure behavior for unsupported dates.

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?

A single dense sentence preceded by a bracketed payment/network prefix; every clause adds information (rate, date, method, attribution, determinism). The paid-metadata prefix occupies the leading position, but for a metered x402 endpoint that is arguably the most decision-relevant fact.

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?

For a zero-argument, single-purpose rate lookup with no output schema, the description covers source, methodology, included fields (rate date, method, source attribution), determinism, and payment requirements. Very little an agent needs in order to call this correctly 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 and the baseline of 4 applies. The description correctly implies the call needs no arguments because the currency pair is fixed in the tool name.

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?

States a specific resource (official EUR/ISK reference rate) and its provenance (ECB fixing, or official peg when ISK is pegged), which is far more than the name alone conveys. It does not explicitly distinguish itself from generic siblings such as fx_convert, fx_latest, or fx_timeseries, so an agent must infer the point-in-time, pair-fixed nature of this call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'latest' implies a current-spot use case, but there is no explicit when-to-use statement, no when-not guidance, and no named alternative in a sibling family of hundreds of near-identical fx_<base>_<quote> tools plus fx_latest, fx_convert, and fx_timeseries. An agent receives no routing guidance at all.

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