Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aed_dkk

[PAID $0.002 USDC/call, x402, eip155:8453] Official AED/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_aed_dkk"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does add real behavioral context: a $0.002 USDC charge via x402 on eip155:8453, the peg-derived fallback when DKK is pegged, ECB attribution, and a determinism/no-estimate guarantee. What is missing is staleness or freshness semantics (how old a “latest” fixing can be, weekend/holiday behavior) and any note on caching or idempotency, which matter for a paid call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the payment/transport bracket, then the resource, then the returned fields, then the quality guarantee. Every clause carries information: source, fallback, date, method, attribution. No filler or restatement of the name.

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, no-output-schema read tool, the description covers everything an agent needs: what currency pair, which authority, what the returned payload contains (rate, rate date, method, attribution), the cost and payment rail, and the fallback path. Nothing structural is left unexplained.

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 the schema has nothing to explain and the baseline of 4 applies. The description correctly adds no parameter discussion and instead spends its words on output provenance, which is the right allocation.

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?

The description names a precise resource: the official AED/DKK reference rate sourced from the latest ECB fixing, including the peg fallback case. That is far more specific than the bare tool name, but it never contrasts itself with siblings like fx_latest, fx_convert, or fx_timeseries, so an agent still has to infer whether this is the single-pair or bulk endpoint.

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 implied rather than stated: “latest European Central Bank fixing” suggests a point-in-time rate lookup, and “no estimate” hints at when a sourced official rate is required over a computed one. There is no explicit when-to-use, when-not-to-use, or named alternative (fx_latest for all pairs, fx_convert for conversion math).

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