Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_qar_chf

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/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 on cost ('$0.002 USDC/call, x402, eip155:8453'), source (ECB fixing) and fallback semantics ('official peg when CHF is pegged'). It stays silent on failure modes, data freshness/lag, and whether stale or holiday fixings are returned, which matters for a paid deterministic-rate endpoint.

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 dense sentences with the price tag and source front-loaded, then the returned attributes. No filler; the only small cost is that the bracketed x402 preamble competes with the core purpose for the first tokens.

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?

There is no output schema, yet the description enumerates the salient return fields — rate, rate date, method (direct/cross via EUR/peg-derived) and source attribution — so an agent knows what it gets. Precision, quoting convention and error payloads are the remaining unknowns for a payment-gated FX endpoint.

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; there are no inputs to disambiguate. The description correctly implies no caller-supplied currency pair or date, since both are fixed by the tool name.

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?

The description names a specific verb+resource: 'Official QAR/CHF reference rate' sourced from 'the latest European Central Bank fixing'. That is clearly distinct from fx_convert, fx_latest and fx_timeseries, and from the inverse fx_chf_qar, though the direction convention (QAR per CHF vs CHF per QAR) is left implicit for an agent to infer from the name ordering.

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: 'reference rate ... no estimate' signals this is the tool for a deterministic, sourced fixing rather than a derived conversion. It never explicitly says when to prefer fx_convert or fx_latest over this pair-specific tool, nor does it give prerequisites such as needing a paid x402 wallet before calling.

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