Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aud_ils

[PAID $0.002 USDC/call, x402, eip155:8453] Official AUD/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_aud_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, the description carries the full burden and does well: it discloses the paid x402 access model ($0.002 USDC/call on eip155:8453), the authoritative source (ECB), the peg fallback path, the method used (direct, cross via EUR, or peg-derived), and that no estimation occurs. It does not state fixing cadence (daily ECB publication, weekend/holiday gaps) or what happens when no fixing exists, which are the remaining behavioral unknowns.

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 price/payment metadata an agent must know before calling, then the resource definition. It is dense but every clause carries information (source, method, fallback, no-estimate guarantee); the second sentence runs long but is not padded.

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 0-param, no-output-schema lookup, the description covers cost, source, fallback logic, and the key returned fields (rate date, method, source attribution). Missing only freshness/caching semantics and error behavior for non-fixing days, which keeps it short of full completeness.

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 further the description could add about inputs. The pair is fully baked into the tool identity, which is the correct design for a 0-param endpoint.

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?

The description names the exact resource (AUD/ILS reference rate) and its provenance (ECB fixing, or official peg when ILS is pegged), so the pair and data source are unambiguous. Against a sibling set of hundreds of fx_* pair tools, the explicit currency pair and source statement make it clear which tool this is 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 only implied: an agent can infer it should call this when it needs an AUD-to-ILS reference rate, and the peg clause hints at the ILS edge case. There is no explicit guidance on when to prefer this over fx_convert, fx_latest, or the cross-pair tools such as fx_aud_eur plus fx_eur_ils, and no stated exclusions.

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