Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_chf_jpy

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description still discloses the $0.002 USDC per-call charge, x402 payment protocol, and eip155:8453 network. It also explains source, freshness, possible derivation methods, determinism, and the returned date and attribution, providing strong behavioral context for a read-only lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is compact and front-loads the material cost and payment requirements before stating the rate, source, methodology, and returned metadata. Despite the technical density, each phrase supplies actionable information and there is no substantial filler.

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

Completeness5/5

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

For a zero-input reference-rate tool without an output schema, the description covers the essential invocation and result context: price, payment network, pair, source, latest-fixing behavior, rate date, derivation method, and attribution. An agent has enough information to call it correctly and interpret the provenance of the result.

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?

There are no parameters to document, so the empty schema is sufficient for invocation. The description usefully reinforces that this is a fixed-pair, latest-rate operation rather than one accepting a date, amount, or currency-pair input.

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 precisely identifies the resource as the latest official CHF/JPY reference rate and names the ECB fixing or peg-derived fallback as its basis. The fixed pair, latest-fixing scope, and provenance distinguish it from generic conversion, latest-rate, and timeseries siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear selection context: use this for a deterministic, sourced official reference rate rather than an estimate, with the latest available fixing and its rate date. It does not explicitly route users away from fx_convert, fx_latest, or fx_timeseries for conversions, other pairs, or historical data.

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