Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_jpy_nzd

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

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?

No annotations exist, so the description carries the full burden and does fairly well: it discloses the paid cost and protocol (PAID $0.002 USDC/call, x402, eip155:8453), the upstream source (ECB), the derivation method (direct, cross via EUR, or peg-derived), and that values are deterministic rather than estimated. What it does not cover is failure behavior (missing fixings, weekends/holidays), rate limits, or the payment/settlement flow beyond naming x402.

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 tight sentence with no filler; every clause (price, source, method, determinism) adds information. The one structural weakness is that the paid-invocation preamble leads, pushing the actual resource description behind the cost notice.

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 usefully enumerates what comes back: the rate, the rate date, the derivation method, and source attribution. Combined with the cost disclosure, an agent has enough to decide and to cite the result; only error/availability conditions 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 the baseline is 4 and there is nothing for the description to disambiguate. It correctly avoids inventing arguments or implying optional filters.

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 names a concrete resource (JPY/NZD reference rate) and the exact provenance of the value (latest ECB fixing, or official peg when NZD is pegged). The pair direction is explicit in the tool name and restated as part of the resource, so an agent can distinguish it from fx_nzd_jpy or the other pair tools without opening anything.

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: 'latest ECB fixing' signals this returns the current spot reference, not history, and 'no estimate' signals it is not a modeling tool. It never names siblings such as fx_convert, fx_timeseries, fx_latest or fx_usd_jpy cross-rates, so the agent must infer when this is preferable to a converted or historical 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