Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cny_dkk

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

No annotations, so the description must carry behavior. It does disclose useful traits: ECB as source, the method alternatives (direct, cross via EUR, peg-derived), deterministic behavior with 'no estimate', and the $0.002 USDC x402 charge on Base. It says nothing about failure when no fixing exists, data staleness, or response shape, leaving real gaps for a paid tool.

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?

Front-loads the currency pair and source in one dense sentence, then a three-word quality claim. The billing preamble is slightly cluttered but carries real pricing information; no wasted sentences.

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

Completeness3/5

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

For a zero-parameter, no-output-schema tool the description covers source, method and pricing, which is most of what is needed. It omits the returned fields beyond date and method, holiday/fallback behavior, and error cases, so it is adequate rather than complete.

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?

Zero parameters, baseline 4. No input semantics are needed, and the description implicitly fixes direction as CNY base to DKK quote, which matters because the reverse-direction sibling also exists.

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 specific resource with source and scope: 'Official CNY/DKK reference rate: latest European Central Bank fixing (or the official peg when DKK is pegged)', plus the derivation method. Among hundreds of near-identical fx_* siblings this pins down exactly the pair and the data provider.

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 by the pair name and source, but there is no explicit when-to-use guidance versus fx_convert, fx_latest, or the reverse fx_dkk_cny tool, and no exclusions or conditions. An agent must infer routing from the name alone.

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