Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_isk_jpy

[PAID $0.002 USDC/call, x402, eip155:8453] Official ISK/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_isk_jpy"
  }
}

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 are supplied, so the description carries the full burden and does well: it discloses the x402 micropayment ($0.002 USDC/call, eip155:8453), the authoritative source (ECB fixing), the fallback behavior when JPY is pegged, and the derived-rate methods (direct, cross via EUR, peg-derived). Remaining gaps are error/staleness behavior and response shape, which are minor given how much source and provenance detail is already front-loaded.

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 dense sentence, front-loaded with the price and chain, then the resource, then the provenance qualifiers. Every clause earns its place; only the parenthetical '(or the official peg when JPY is pegged)' is slightly tangled.

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 and no annotations, the description must carry everything, and it enumerates what comes back (rate, rate date, method, source attribution) plus the determinism guarantee. That covers the essentials for a zero-parameter lookup; only explicit response-field naming or staleness/freshness bounds are missing.

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 parameter talk and instead spends its words on the fixed pair and data provenance.

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?

States a specific resource with a precise verb: 'Official ISK/JPY reference rate: latest European Central Bank fixing'. The pair is fixed in the name and confirmed in prose, so an agent can tell it apart from the ~600 sibling fx_* pairs without opening a 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 by the currency pair and by 'latest ECB fixing', but the description never routes the agent to the relevant alternatives that exist as siblings (fx_convert for arithmetic conversion, fx_latest for cross-pair lookups, fx_timeseries for history), nor does it state when-not to use this tool.

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