Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_nok_aed

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/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 disclose two important traits: the call is paid ($0.002 USDC via x402 on eip155:8453) and the value degrades to an official peg when AED is pegged rather than falling back to a cross rate. It does not state what happens on a non-fixing day, whether EUR crosses are recomputed, or how payment/errors are surfaced, so coverage is partial for a paid endpoint.

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?

One dense sentence after the pricing prefix, with the price/mechanism tag front-loaded and the purpose immediately after. Slightly packed ('cross via EUR or peg-derived', 'source attribution') but every clause carries information.

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 exists, and the description compensates by enumerating the returned components: rate, rate date, computation method and source attribution. For a zero-parameter single-value lookup that is close to complete, with the main remaining gap being stale-data or holiday/failure behavior.

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 input parameters, so there is no schema semantics to compensate for; the baseline applies. The description instead spends its words on the semantics of the returned fields (rate date, method, source attribution), which is the relevant meaning here.

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 (official NOK/AED reference rate) and a specific source (latest ECB fixing), plus the peg fallback. The currency pair in the name plus the stated source make it unambiguously distinct from the hundreds of sibling fx_* pair tools.

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?

There is no explicit statement of when to use this versus fx_convert, fx_latest or fx_timeseries, which are the obvious alternatives for rate retrieval. The phrase 'Deterministic, sourced, no estimate' implicitly signals audit/reference-grade use over ad-hoc conversion, but the agent must infer that routing itself.

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