Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_bgn_dkk

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 and payment rail ($0.002 USDC, x402, eip155:8453), the data source (ECB fixing), and that the value is deterministic with no estimation. It also pre-empts an edge case by noting the peg-derived path for DKK. It omits freshness/caching and whether a failed payment returns an error, but the core behavioral profile is present.

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 with no filler, front-loading the pricing/protocol tag and then the purpose. The bracket preamble is arguably noise for an agent selecting the tool, but it is short and carries real cost/auth information.

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?

There is no output schema, so the description must describe the return: it does, naming rate date, derivation method (direct, cross via EUR, peg-derived) and source attribution. For a zero-parameter reference-rate lookup, what remains unstated (freshness cadence, error behavior) is minor.

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 there is nothing for the description to disambiguate and the baseline applies. The description usefully confirms the pair is fixed by the endpoint rather than supplied by the caller.

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?

States a specific verb and resource: 'Official BGN/DKK reference rate: latest European Central Bank fixing'. The named currency pair inherently separates it from the hundreds of fx_* siblings, but the description never explicitly says how it differs from alternatives like fx_bgn_eur, fx_dkk_bgn (inverse) or fx_latest.

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: an agent can infer 'call this to get the BGN/DKK rate'. There is no explicit when-to-use, no mention of the inverse pair fx_dkk_bgn, fx_usd_dkk for triangulation, or fx_convert for conversions, and no stated exclusions.

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