Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_dkk_qar

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description discloses the $0.002 USDC per-call charge, x402 payment mechanism, and eip155:8453 network, as well as determinism and non-estimated sourcing. It also explains the possible derivation methods and states that results include the rate date, method, and source attribution.

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?

The compact text front-loads cost and payment requirements, then efficiently covers purpose, provenance, returned metadata, and determinism without filler. Its parentheticals are dense but convey useful payment and methodology details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-input, fixed-pair latest-rate lookup, it supplies the pair, recency, authority, derivation options, determinism, and exact payment terms needed to select and invoke it. Despite the absence of an output schema, it also identifies the important result context: rate date, method, and source attribution.

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 schema has zero parameters, so there are no inputs requiring further semantic explanation. The fixed currency pair is fully identified in the description, meeting the zero-parameter baseline without introducing nonexistent options.

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?

The description identifies the exact resource and scope: the latest official DKK/QAR reference rate, based on an ECB fixing or an official peg. “Latest” and “reference rate” help distinguish it from sibling conversion and historical tools such as fx_convert and fx_timeseries.

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?

It gives a clear use case: obtain a current, official, sourced DKK/QAR reference rate rather than an estimate. It does not explicitly direct amount-conversion requests to fx_convert or historical requests to fx_timeseries, so alternative selection still requires some inference.

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