Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sgd_dkk

[PAID $0.002 USDC/call, x402, eip155:8453] Official SGD/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_sgd_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?

No annotations are supplied, but the description carries the important operational facts itself: a paid call at $0.002 USDC, x402 protocol, chain eip155:8453. It also discloses the data-handling behavior an agent needs for trust — deterministic, sourced, no estimate, peg-derived fallback when DKK is pegged. It does not cover failure modes (what happens if payment fails or no fixing is available) or caching/freshness windows.

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 front-loaded sentence with the payment terms first, then the data guarantee. Dense but every clause carries signal; the only mild redundancy is "Deterministic, sourced, no estimate," which restates the preceding description of the fixing.

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?

With no output schema, the description must describe the payload, and it does: rate, rate date, method (direct/cross via EUR/peg-derived), and source attribution. Combined with the zero-parameter schema and the stated payment cost, an agent has enough to invoke it correctly; only error and freshness behavior are left unstated.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly adds no spurious parameter guidance.

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?

The description names the exact resource ("Official SGD/DKK reference rate") and its provenance ("latest European Central Bank fixing"), which is enough to distinguish it from the other pair-specific fx_* siblings by currency code alone. It stops short of naming related siblings such as fx_convert or fx_timeseries, so an agent must infer the boundary from the pair name rather than being told.

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 needing an SGD/DKK rate on ECB terms is the obvious caller. There is no statement of when to prefer fx_convert (arbitrary pair) or fx_timeseries (historical series), and no note about whether the result is safe to reuse or should be re-fetched per call.

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