Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_jpy_cad

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description provides substantial operational context: the exact per-call price, x402 payment rail and network, authoritative source, possible derivation methods, returned provenance, and deterministic/no-estimate behavior. It does not explain ECB publication timing, weekend or holiday staleness, or failure behavior when a fixing is unavailable.

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 compact sentences front-load payment requirements and then clearly state the resource, source, methodology, and returned metadata. The chained parentheticals and conditional peg caveat make the text somewhat dense and add detail that rarely helps selection or invocation.

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-input lookup without an output schema, the description covers the pair, recency, source, derivation methods, rate date, attribution, determinism, and cost. It would be more complete with an explicit quote convention and units, such as CAD per one JPY, plus staleness conventions and pointers to the principal sibling alternatives.

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, so the zero-parameter baseline applies and there are no undocumented inputs to compensate for. Fixing the currency pair in the name and description is sufficient for invocation.

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 identifies a fixed JPY/CAD lookup returning the latest official ECB reference fixing, including its derivation and attribution, rather than merely restating the tool name. The fixed pair, 'latest' scope, and 'reference rate' framing distinguish it from other pair tools, fx_timeseries, and conversion-oriented fx_convert.

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?

The wording establishes a clear use case: obtaining a current, authoritative JPY/CAD reference rate with provenance rather than an estimate. It does not explicitly route agents needing amount conversion, history, or a dynamically selected pair to fx_convert, fx_timeseries, or fx_latest.

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