Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xaf_czk

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 per-call price, USDC payment requirement, x402 protocol, blockchain network, deterministic behavior, provenance, and possible calculation methods. It does not explicitly address read-only behavior, publication freshness, or what happens when a fixing is unavailable.

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?

The definition is compact and front-loads the material payment cost before giving the rate scope, returned metadata, and sourcing behavior. The long parenthetical method list and repeated ideas such as 'source attribution' and 'sourced' make it slightly dense and redundant.

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-argument lookup without an output schema, the description covers the fixing source, rate date, method, attribution, and payment requirements well. It would be more complete with explicit direction and units, such as CZK per one XAF, plus freshness or unavailable-fixing behavior and guidance on relevant sibling tools.

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 the baseline score of 4 applies. Its fixed XAF/CZK pair and latest-rate scope explain why no pair, date, or amount arguments are needed.

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 clearly identifies the resource as the latest official XAF/CZK reference rate and names the ECB as its fixing source. It does not explicitly differentiate this pair-specific lookup from siblings such as fx_latest, fx_convert, or fx_timeseries.

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?

The terms 'latest,' 'official,' and 'no estimate' establish a clear context: obtaining a current, sourced reference rate rather than an estimated value. However, there is no explicit routing guidance for agents needing currency conversion, historical observations, or multiple rates.

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