Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_usd_chf

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 load and does well: it discloses the paid access model ($0.002 USDC/call, x402, eip155:8453), the determination method (direct, cross via EUR, or peg-derived), the source attribution, and that results are deterministic and never estimated. It stops short of describing the response shape or error behavior when no fixing is available.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single information-dense sentence with the cost/access prefix up front and the substantive guarantee ('deterministic, sourced, no estimate') closing it. Every clause adds a distinct fact; 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 zero-argument lookup with no output schema and no annotations, the description covers the important ground: source authority, method variants, peg fallback, and the fields returned (rate date, method, attribution). Only the concrete response format and failure mode are left unstated.

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 no argument semantics to explain and the baseline is 4. The description correctly conveys that no inputs are needed by naming the fixed currency pair in the tool purpose itself.

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 verb-and-resource pair ('Official USD/CHF reference rate: latest European Central Bank fixing'), including the fallback to an official peg. It does not, however, distinguish itself from close siblings such as fx_latest, fx_timeseries, or fx_convert, nor note that fx_chf_usd is the inverse pair.

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: call this when you need the official USD/CHF ECB reference rate rather than a market quote. There is no explicit when-not guidance, no pointer to alternatives (fx_convert for conversions, fx_timeseries for history), and no stated precondition beyond the payment.

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