Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cny_ils

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

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 supplied, the description carries the full burden, and it does meaningful work: it discloses the payment requirement and protocol (PAID $0.002 USDC/call, x402, eip155:8453), the upstream authority (ECB), and the fallback behavior for a pegged currency. It omits failure modes — what happens if no fixing exists for a date — but the cost/auth disclosure is exactly the kind of context annotations would otherwise have to cover.

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 with no wasted clauses. The price/protocol tag is front-loaded in brackets, which is easy to scan but slightly displaces the actual purpose; the substance still arrives immediately after.

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 zero-parameter, no-output-schema lookup, the description covers source, method (direct/cross via EUR/peg-derived), date, and attribution — essentially the return payload in prose. Error and staleness behavior are the only real gaps.

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 at the input level. Baseline 4 applies; the description adds that the pair and source are fixed rather than caller-specified.

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?

States a specific resource (CNY/ILS reference rate) and pins the exact source and vintage ('latest European Central Bank fixing', or the official peg when pegged). The pair is unambiguous, so an agent won't confuse it with the other fx_* tools. It stops short of naming the sibling it differs from conceptually (fx_convert, fx_latest, fx_timeseries), so it isn't a full 5.

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 infers you call this when you need the official CNY-to-ILS reference rate. There is no explicit when-to-use/when-not, and no pointer to fx_convert for arithmetic conversion or fx_timeseries for historical series, which are the natural alternatives an agent would weigh.

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