Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_hkd_dkk

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 cost ($0.002 USDC/call), the x402 payment scheme and chain (eip155:8453), the data source (ECB), the derivation method (direct, cross via EUR, or peg-derived), and the determinism guarantee. It stops short of stating freshness/staleness rules (e.g., weekend or holiday carry-forward) or failure behavior when no fixing is available.

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?

A single dense sentence preceded by the pricing/payment tag, front-loading cost then purpose then output shape. Every clause adds information an agent needs (source, method, return fields, determinism) with 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 tool with no output schema, the description must explain the return shape, and it does: rate date, method, and source attribution are all named. The remaining gap is freshness semantics, which matters for a "latest fixing" tool but is not addressed.

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, which is the baseline-4 case; the description correctly implies a fully self-contained call with nothing to supply. No additional parameter meaning is needed or missing.

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?

"Official HKD/DKK reference rate: latest European Central Bank fixing" names a specific resource and its authoritative source, so an agent knows exactly what value it gets. It does not explicitly contrast itself with siblings such as fx_convert or fx_timeseries, leaving the pair-name alone to carry differentiation.

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 ... fixing" signals a point-in-time spot lookup, and "no estimate" warns against treating it as a model output. There is no explicit when-to-use/when-not guidance pointing to fx_convert for amount conversion or fx_timeseries for historical series.

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