Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_mxn_dkk

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 paid x402 flow, price ($0.002 USDC), network (eip155:8453), and key behavioral traits — deterministic output, authoritative sourcing, no estimation, and peg-fallback handling for DKK. It omits freshness cadence (when the ECB fixing lands) and failure/error behavior for non-trading days.

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 with the cost/payment constraints front-loaded in brackets, followed immediately by the substantive definition. Every clause — peg fallback, rate date, derivation method, attribution, 'no estimate' — adds distinct information; there is no filler.

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-param, no-output-schema tool, the description adequately characterizes what comes back (rate value, rate date, derivation method, source attribution) plus the payment precondition. It stops short of specifying numeric precision, exact field shape, or how to handle weekends/holidays when no fixing exists.

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 baseline applies; the currency pair is fully encoded in the tool name and restated in the description, leaving nothing for the caller to specify. There is no schema content to add meaning to.

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 precise verb+resource: the official MXN/DKK reference rate, sourced from the latest ECB fixing, with a named fallback (official peg when DKK is pegged). The pair direction and the authoritative-vs-estimate distinction are unambiguous, and the source attribution (ECB) separates it from any derived or estimated sibling rate 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?

Usage is only implied: 'deterministic, sourced, no estimate' hints at reference/accounting use cases, and the payment prefix signals a pay-per-call model. It gives no explicit when-to-use guidance, no mention of the sibling inverse pair (fx_dkk_mxn) or conversion tools like fx_convert/fx_latest, and no when-not conditions.

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