Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_usd_ils

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

With no annotations supplied, the description carries the full load and does well: it discloses the paid access model and price ("$0.002 USDC/call, x402, eip155:8453"), the data source, the derivation method (direct, cross via EUR, or peg-derived), and that the result is deterministic rather than estimated. It stops short of describing freshness lag or failure behavior when no fixing is published, which keeps it off a 5.

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 sentences, front-loaded with the paid-access tag and then the core definition, with no filler. The bracketed cost/network metadata is dense but genuinely useful. Minor cost: the parenthetical method clause makes the second sentence long.

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 hint at return content, and it does by naming the rate date, derivation method, and source attribution as returned fields. A little more on staleness (how recent the 'latest' fixing is) would make it fully self-sufficient for a zero-param, unannotated tool.

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 there is nothing for the description to disambiguate beyond the pair itself, which the name and description fix precisely. Baseline of 4 applies for a no-parameter tool.

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 an unambiguous currency pair and names the authoritative source ('Official USD/ILS reference rate: latest European Central Bank fixing'), including the fallback case for a pegged ILS. An agent can distinguish this from the hundreds of sibling fx_* tools purely from the pair and source framing.

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?

Implies the use case (retrieve the current official USD/ILS rate) and clarifies that the peg path applies when ILS is pegged, but never names alternatives such as fx_latest, fx_timeseries, or fx_convert, nor states when to prefer a cross rate. Usage is inferable but not directed.

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