Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xaf_mxn

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

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, the description carries the full burden and does well: it discloses the paid x402 model ($0.002 USDC/call on eip155:8453), that the data is a deterministic, sourced official fixing rather than an estimate, and that output includes rate date, derivation method and source attribution. It does not describe behavior on stale data, payment failure, or update cadence.

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?

A single dense sentence plus a bracketed payment tag; every clause earns its place (rate, source, peg fallback, return fields, determinism). The cost/x402 tag is front-loaded as a convention, though it precedes the actual purpose, which slightly delays the core statement.

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 and no annotations, yet the description enumerates the return payload (rate, rate date, method, source attribution) and the payment mechanism, which covers the main gaps. The notable omission is quote direction — whether the rate is XAF per MXN or the inverse — plus freshness cadence, which matters for a rate lookup tool.

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 at the input layer and the baseline is a 4. The pair is baked into the tool name, which the description confirms.

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?

Names the exact resource (official XAF/MXN reference rate) and pins down the source and nature of the value (ECB fixing, or the official peg when MXN is pegged). It clearly separates this pair-specific tool from the hundreds of sibling fx_* pairs, but it is a noun phrase with no explicit verb and never distinguishes it from general siblings like fx_convert or fx_latest.

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: an agent can infer it is the tool for the XAF/MXN reference rate specifically. There is no explicit statement of when to prefer it over fx_convert (arbitrary pair conversion) or fx_latest, and no prerequisites or failure conditions are given.

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