Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_jpy_kmf

[PAID $0.002 USDC/call, x402, eip155:8453] Official JPY/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_jpy_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?

No annotations exist, so the description carries the full burden, and it discloses the important traits: paid access ($0.002 USDC/call via x402 on eip155:8453), deterministic, sourced, no estimation, and that a peg may be returned instead of a market fix. It stops short of saying how fresh the fixing is (daily ECB publication timing) or what happens on weekends/holidays.

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?

One front-loaded sentence with the resource and the returned fields, plus a short qualifier about determinism and sourcing. The x402 pricing prefix occupies the most prominent slot and is moderately noisy, but every remaining clause adds real information.

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-parameter, no-output-schema lookup tool the description covers what is returned (rate, date, method, source) and the payment model, which is what an agent needs before calling. The main omission is expected data freshness and behavior when no fixing exists for the date.

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; the description correctly clarifies that no currency pair or date argument is needed because the pair and rate date are fixed/returned by the call.

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 a specific resource (the JPY/KMF reference rate) and states exactly what value is returned: the latest ECB fixing, the rate date, the derivation method (direct/cross via EUR/peg-derived) and the source. Against hundreds of sibling fx_* pair tools the pair identity plus 'ECB fixing' is enough to tell it apart without opening the schema.

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 implied rather than stated: it is a single-pair reference-rate lookup, but the description never says when to prefer it over siblings like fx_latest, fx_convert or fx_timeseries, nor any exclusion such as 'not for historical series'. Implied-by-scope only.

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