Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xaf_dkk

[PAID $0.002 USDC/call, x402, eip155:8453] Official XAF/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_xaf_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 supplied, the description usefully discloses the $0.002 USDC per-call cost, x402 payment requirement, eip155:8453 network, deterministic behavior, provenance, and possible calculation methods. It does not explicitly address read-only behavior, availability failures, or how stale or missing fixings are handled, so it is informative but not exhaustive.

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?

Two compact sentences convey payment requirements, purpose, recency, source, returned metadata, methodology, and determinism without filler. Although dense, the parentheticals are substantive and the invocation-critical payment information is appropriately front-loaded.

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-input lookup, the description covers the pair, authority, recency, cost, payment mechanism, rate date, method, and source attribution, which is enough for straightforward selection and invocation. With no output schema or annotations, clarifying the exact quote convention and unavailable-fixing behavior would remove the remaining modest ambiguity.

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 has zero parameters, so the no-parameter baseline of 4 applies. The fixed currency pair and latest-rate behavior mean no input semantics are needed for invocation.

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 clearly identifies the resource as the latest official XAF/DKK reference rate and specifies its ECB fixing or peg-derived basis. The fixed pair and latest-reference scope help distinguish it implicitly, but it does not explicitly differentiate itself from fx_latest, fx_convert, fx_timeseries, or the reverse-pair sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Phrases such as "latest," "Official," and "no estimate" provide clear context for choosing this tool when a sourced current reference rate is needed. However, there are no explicit when-not conditions or directions to alternatives for currency conversion, historical series, or the opposite quote direction.

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