Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xof_czk

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

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 disclose meaningful behavior: pay-per-call pricing ($0.002 USDC via x402 on eip155:8453), determinism, source attribution, returned rate date, and the derivation method including the peg fallback. It does not cover failure behavior (e.g. what happens on a non-publication day or insufficient payment), which keeps it below 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 compact clauses, front-loaded with payment terms and then the substantive definition; every clause adds information (rate, date, method, attribution, determinism). The bracketed payment tag is slightly noisy but is legitimately actionable for an agent deciding whether to call.

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, so the description must describe the return value, and it does: rate, rate date, method (direct/cross via EUR/peg-derived), and source attribution. Given a zero-parameter tool, the remaining gap (direction of quotation, staleness/latency) is minor.

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?

Zero parameters, so the baseline is 4; the description correctly signals that no inputs are needed beyond the call itself. The only ambiguity is the quote convention (which currency is the base), which the schema cannot resolve either.

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?

States the exact resource (official XOF/CZK reference rate) and its provenance (latest ECB fixing, or official peg when CZK is pegged), which is more specific than the name alone. It does not explicitly distinguish itself from the many sibling fx_* pair tools or from fx_convert/fx_latest/fx_timeseries, so an agent must infer that this is a single-pair, latest-only lookup.

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?

Implied usage is clear enough (you want the official XOF/CZK reference rate, not a market quote), and the peg caveat hints at when results differ. However, there is no explicit when-to-use/what-to-use-instead guidance relative to fx_convert, fx_latest, or fx_timeseries, which is a real risk in a catalog of hundreds of near-identical pair tools.

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