Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_idr_dkk

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

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 no annotations, the description does real work: it discloses the paid x402 model ($0.002 USDC/call on eip155:8453), the upstream source, the fallback derivation path (direct / cross via EUR / peg-derived), and that the result is deterministic rather than an estimate. It omits rate limits, error behavior on non-publishing days (weekends/holidays), and how stale a fixing can be.

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 dense, waste-free sentences covering cost, purpose, derivation and guarantees. The payment tag is front-loaded ahead of the actual purpose, which is slightly awkward ordering for an agent scanning for what the tool does.

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 no-parameter, no-output-schema tool the description covers what is returned (rate, date, method, attribution) and the pricing/access model. Remaining gaps — freshness policy and failure modes — are modest but real given there is no output schema to fall back on.

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-parameter tool, so the baseline is 4; the description correctly implies the pair and source are fixed by the tool itself. It adds no parameter guidance because none is needed.

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?

Names the exact resource (IDR/DKK reference rate), the authoritative source (ECB fixing, or the official peg when DKK is pegged), and the returned facets (rate date, derivation method, source attribution). An agent can distinguish this from the hundreds of sibling pair tools and from fx_convert/fx_timeseries without opening any 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: 'reference rate' hints at point-in-time official fixing rather than conversion or history, but the description never says when to pick this over fx_convert (amount conversion), fx_latest, or fx_timeseries. No exclusions or prerequisites beyond the payment tag are stated.

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