Skip to main content
Glama

Novarithm Agent Hub: trust and commerce checks

fx_mxn_chf

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 cost ($0.002 USDC/call), payment protocol/network (x402, eip155:8453), data source (ECB), peg fallback behavior, returned method (direct/cross/peg), and that values are deterministic and non-estimated. Missing only edge behavior such as update cadence or handling of non-fixing days.

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 sentence with no filler; the bracketed payment metadata front-loads cost info an agent needs before calling, though that prefix slightly delays the substantive purpose 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?

No output schema exists, so the description must describe the return, and it does: rate, rate date, calculation method, and source attribution. For a zero-parameter, single-value lookup this is nearly complete; only the refresh cadence or holiday/weekend behavior is 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 the baseline of 4 applies; the description correctly requires no parameter explanation and adds no confusing parameter claims.

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?

States a specific verb and resource — the official MXN/CHF reference rate from the latest ECB fixing — and names the exact scope (MXN/CHF) so it is distinguishable from the many sibling pair tools and from fx_convert/fx_timeseries without opening a schema.

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

Usage Guidelines2/5

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

Implies it returns the latest fixing, which loosely excludes historical queries, but never states when to use it versus siblings such as fx_convert, fx_latest, or fx_timeseries for history. No explicit exclusions or prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.