Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aud_kmf

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 substantial work: it discloses the payment model and price ($0.002 USDC/call, x402, eip155:8453), the upstream source (ECB fixing), the fallback (official peg when KMF is pegged), and the derivation method (direct, cross via EUR, peg-derived). It does not state failure behavior when no fixing is available, caching/staleness windows, or how the x402 payment handshake is completed.

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?

Two sentences, front-loaded with the price/payment tag followed immediately by the resource and its provenance guarantees. The bracketed payment metadata is dense but earns its place for an agent that must decide whether a paid call is affordable; nothing is redundant.

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?

No output schema exists, and the description compensates by enumerating the returned fields — rate, rate date, method, and source attribution — so the agent knows what comes back. For a zero-parameter lookup this is close to complete; only error/staleness handling is left unspecified.

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 meaning to explain; the fixed currency pair is already encoded in the name. Baseline of 4 applies, with no gap for the description to compensate for.

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?

Names the exact resource ("Official AUD/KMF reference rate") including the base/quote pair, and specifies what the returned value represents versus an estimate. Among hundreds of fx_* siblings, an agent can tell instantly this is the AUD→KMF pair and not the inverse or a converter.

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: "Deterministic, sourced, no estimate" signals it should be preferred when an official reference rate is required rather than a market quote. It never names alternatives such as fx_convert (for arithmetic conversion) or fx_timeseries/fx_latest (for history or a bulk snapshot), so the 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