Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_kmf_usd

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

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 zero annotations the description carries the full load, and it discloses the commercially critical behavior up front: $0.002 USDC per call over x402 on eip155:8453. It also commits to deterministic, sourced values rather than estimates and explains the method/attribution returned. It stops short of error, latency, or caching behavior.

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?

Essentially two sentences, front-loaded with the price/scheme tag and then the substantive rate description. Dense but every clause (source, peg fallback, method, attribution) adds information; only the bracketed payment tag could be trimmed by an agent that already knows the scheme.

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, no-output-schema tool, the description compensates well by previewing the return contents (rate, rate date, method, source attribution). Missing only quote precision/format and how stale the ECB fixing can be, which an agent pricing a payment decision would want.

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 an empty object, so there are no parameter semantics to explain and no gap to compensate for. Baseline for a zero-parameter tool applies.

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?

Names a specific resource and direction ('Official KMF/USD reference rate') plus the underlying source (ECB fixing) and the peg fallback, so the agent knows exactly which quote it gets. It does not differentiate against the inverse sibling fx_usd_kmf or the generic fx_latest/fx_convert, which is the one gap keeping it from a 5.

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 infers it should call this when it needs a KMF-to-USD rate. There is no explicit when-to-use vs fx_usd_kmf, fx_latest, fx_convert or fx_timeseries, and no statement about freshness or when a direct rate is unavailable.

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