Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aed_ils

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

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 largely discharges it: cost ($0.002 USDC), protocol and chain (x402, eip155:8453), upstream source (ECB fixing, or the official peg when ILS is pegged), derivation method, and an explicit 'deterministic, sourced, no estimate' guarantee. It stops short of failure modes, staleness/TTL, or behavior on non-fixing days.

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 dense sentence with the paid-tier metadata front-loaded in brackets, then purpose, then the returned attributes. Every clause carries information. Slightly overstuffed as a single sentence, but nothing is redundant.

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 parameterless rate lookup with no output schema, the description supplies what the response contains (rate, date, method, attribution) and the access model, which is what an agent needs to call it. The main remaining gap is data freshness – 'latest fixing' has no stated publication cadence or staleness bound.

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 declares zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly implies no input is needed – the currency pair is baked into the tool name.

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 official AED/ILS reference rate from the ECB – and states exactly what comes back: the rate, its date, the derivation method and the source. Against hundreds of fx_* siblings the pair is unambiguous, and 'official ECB fixing / peg' separates it from a market-quote or estimate tool.

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: fetch the authoritative reference rate for this one pair. But it never routes the agent among its closest siblings – fx_convert for arithmetic on an amount, fx_latest for multiple pairs, fx_timeseries for history – nor does it state prerequisites beyond the payment note. Adequate but leaves selection to inference.

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