Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xaf_cve

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description usefully discloses the $0.002 USDC per-call fee, x402 payment mechanism, eip155:8453 network, source and peg fallback, possible derivation methods, and deterministic behavior. It does not explicitly state that the operation is read-only or explain payment and failure handling, so some operational details remain implicit.

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?

The payment requirement is front-loaded, followed by the purpose, returned metadata, and data-quality guarantees in two compact sentences. The terminology conveys operational information without filler or repetition.

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 lookup, the description covers cost, recency, source, methodology, provenance, and determinism, and it helpfully identifies returned fields despite the absence of an output schema. It would be more complete with explicit XAF-to-CVE quote orientation and routing guidance relative to the generic conversion, latest-rate, and time-series siblings.

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 has zero parameters, so there are no argument semantics requiring additional documentation. The fixed currency pair and latest-rate scope make the no-argument invocation straightforward.

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 identifies the exact XAF/CVE pair and specifies an official, latest reference rate based on the ECB fixing or official peg. Listing the rate date, derivation method, and source attribution further clarifies the resource and distinguishes this official reference lookup from estimation or general conversion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Terms such as "latest," "official," "deterministic," and "no estimate" provide clear context for choosing this tool when a sourced current reference rate is needed. However, it does not explicitly explain when to prefer fx_convert, fx_latest, or fx_timeseries, nor does it exclude amount conversion or historical-rate use cases.

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