Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_eur_zar

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

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 burden well: it discloses that the call is paid ($0.002 USDC per call over x402 on eip155:8453), that the value is a deterministic sourced fixing rather than an estimate, and that the response carries rate date, derivation method and source attribution. It stops short of stating failure behaviour (what happens when no fixing exists, weekend/holiday handling) or rate limits.

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, front-loaded with the pricing/payment banner and then the resource definition; no filler. The trailing 'Deterministic, sourced, no estimate' is slightly clipped but each element adds trust-relevant meaning.

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 tool, the description effectively describes the return payload (rate, rate date, method, source attribution) and the payment protocol, which is what an agent needs to call it and interpret the result. Missing only edge-case behaviour such as unavailable fixings or non-trading days.

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 is nothing for the description to disambiguate, and it correctly spends no text on inputs.

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 a specific resource and scope: the official EUR/ZAR reference rate, the latest ECB fixing (or official peg), plus the rate date, derivation method and source attribution. That is far more precise than the bare pair encoded in the name, and it implicitly separates this from aggregate siblings such as fx_convert, fx_latest and fx_timeseries, which do not pin a single pair and provenance.

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: the fixed EUR/ZAR pair and 'reference rate' framing tell an agent this is the lookup for that one pair, and 'deterministic, sourced, no estimate' hints it is for authoritative/audit use. However, there is no explicit when-to-use/ when-not guidance and no named alternative for conversion of an amount (fx_convert) or for historical series (fx_timeseries), which matters given hundreds of sibling fx_* tools.

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