Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aed_jpy

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the price ($0.002 USDC per call), the payment scheme (x402) and chain (eip155:8453), plus the data lineage and peg fallback behavior. It stops short of describing what happens on unpaid or failed calls and any rate limits.

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 preceded by a bracketed payment tag, with the cost and provenance front-loaded. Almost every clause earns its place; the flag sentence 'Deterministic, sourced, no estimate' is slightly redundant with 'Official ... reference rate' but reinforces trust.

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?

No output schema exists, so the description must explain the return shape, and it does by listing rate date, method (direct, cross via EUR, or peg-derived) and source attribution. Combined with the cost disclosure, an agent has what it needs to call a zero-parameter endpoint correctly.

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 schema is empty, so there are no parameters to explain; the baseline for a zero-parameter tool applies. The description usefully compensates by naming the components returned (rate date, derivation method, source attribution), which is more than the empty schema conveys.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (the AED/JPY reference rate) and a specific source (the European Central Bank fixing), with the peg fallback stated. It is clearly distinguishable from the hundreds of sibling pair tools by the name, but it does not address the other non-pair siblings such as fx_convert or fx_timeseries that an agent might prefer.

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: an agent that needs the AED/JPY reference rate is the intended caller, and 'Deterministic, sourced, no estimate' hints at why to choose this over an estimating service. There is no explicit when-not guidance and no signposting to fx_convert for converting amounts or fx_timeseries for history.

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