Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aed_nok

[PAID $0.002 USDC/call, x402, eip155:8453] Official AED/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_aed_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 zero annotations the description carries the full burden and does well: it discloses the price and payment rail ($0.002 USDC, x402, eip155:8453), the authoritative source (ECB), the peg fallback path, and that results are deterministic rather than estimated. It stops short of stating behavior around non-publication days (weekends/holidays), caching/freshness windows, or error handling, which for a paid-per-call endpoint an agent would want.

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 with no filler; each clause (cost, source, peg fallback, rate date, method, attribution, determinism) carries information. Minor cost: the payment metadata is front-loaded ahead of the actual purpose, so the first thing an agent reads is pricing rather than what the tool returns.

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 close to sufficient: it names the source, the fallback method, and the ancillary fields returned (rate date, direct/cross/peg method, attribution). It does not describe the numeric shape of the response (quote direction, precision, ISO date format), which is the one thing an agent cannot infer from an empty input schema.

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 no parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The prose does implicitly confirm no input is needed by presenting the pair as fixed in the tool identity.

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-level action: the official AED/NOK reference rate, sourced from the latest ECB fixing. The currency pair in the name plus 'European Central Bank fixing (or the official peg)' distinguishes it cleanly from every other fx_* pair sibling without needing 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 only implied: an agent can infer this is the AED-to-NOK spot reference lookup. There is no explicit routing guidance against the obvious alternatives (fx_convert for arithmetic, fx_timeseries for history, fx_latest for a multi-pair snapshot), and no 'when not to use' clause.

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