Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xof_eur

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

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 does well: it discloses the x402 payment protocol, the exact price ($0.002 USDC), the chain (eip155:8453), the upstream source (ECB), and that the value is deterministic rather than estimated. It omits what happens on payment failure or when no fixing is available, which keeps it short of a 5.

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, tightly written, with the cost/protocol banner separated from the substance. The bracketed payment prefix is front-loaded noise for an agent that cannot pay, but it is genuinely decision-relevant for x402 routing and does not bloat the rest of the text.

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, but the description compensates by enumerating the return contents: rate date, derivation method (direct, cross via EUR, or peg-derived), and source attribution. For a zero-parameter, read-only single-value lookup this is nearly complete; only failure modes are 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 nothing for the description to disambiguate and the baseline of 4 applies. The description correctly adds no parameter discussion and instead spends its words on provenance and cost.

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 the exact resource (the XOF/EUR reference rate) and its provenance (the European Central Bank fixing, or the official peg when EUR is pegged), so the pair and source are unambiguous. It does not explicitly contrast itself with neighbours like fx_convert, fx_latest or fx_timeseries, relying on the tool name for pair differentiation.

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: 'reference rate', 'deterministic, sourced, no estimate' signals this is the authoritative fixing tool rather than a converted or estimated quote. There is no explicit when-to-use or when-not guidance pointing at fx_convert/fx_latest/fx_timeseries for derived or historical values.

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