Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_dkk_zar

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

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 carries the full burden and does well: it discloses the $0.002 USDC/call cost, the x402 payment scheme on eip155:8453, the upstream source (ECB), the derivation method (direct, cross via EUR, or peg-derived), and that the result is deterministic and non-estimated. It stops short of describing what happens on non-fixing days or how a missing/pegged rate is surfaced.

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 plus a bracketed payment tag, front-loaded with the cost signal before the data description. Nothing is padded, though the parenthetical '(or the official peg when ZAR is pegged)' and the triple method list make the sentence long enough that it rewards a second read.

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 parameterless lookup with no output schema and no annotations, the description supplies the essentials: source, method, freshness indicator (rate date), attribution, and payment cost. The remaining gap is return-shape specifics (field names, units, quote convention) that an agent would otherwise need an output schema for.

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 the baseline of 4 applies. The description correctly frames this as a parameterless single-pair lookup and adds no misleading argument language.

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 verb and resource: the official DKK/ZAR reference rate, specifically the latest ECB fixing or the official peg. The currency pair in the name is disambiguated in prose, so an agent can tell it apart from the hundreds of sibling fx_* pair tools without opening 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 implied by the pair and the 'reference rate' framing, but there is no explicit routing guidance. It never says when to prefer this over fx_convert, fx_latest, or fx_timeseries, nor does it state whether the pair is inverted versus fx_zar_dkk (which also exists in the sibling list).

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