Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aud_czk

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses the cost and payment rail ($0.002 USDC/call, x402, eip155:8453), the upstream source (ECB), and the derivation method (direct, cross via EUR, or peg-derived) including the peg fallback for CZK. It also asserts determinism and 'no estimate'. What it omits is the payment/failure flow for the x402 handshake.

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?

Pricing and rail are front-loaded in a bracketed prelude, then the substantive description follows in a single dense sentence. The parenthetical enumerating methods is slightly run-on but every clause (date, method, attribution, no-estimate) carries information an agent would otherwise lack.

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 tool with no output schema, the description covers what is returned (rate, rate date, method, source attribution) and its provenance guarantees. The remaining gap is operational: how the x402 payment is settled and what an agent should do if payment or fixing lookup fails.

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; baseline applies. The implicit 'AUD base, CZK quote' directionality is conveyed only by the name, which is sufficient here.

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: 'Official AUD/CZK reference rate: latest European Central Bank fixing', plus what accompanies it (rate date, method, source attribution). The currency pair is embedded so it is trivially distinguishable from the hundreds of sibling fx_<base>_<quote> tools and from fx_convert/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 implied by the pair-specific naming and the 'reference rate' framing, but there is no explicit guidance on when to use this versus fx_convert (actual conversion) or fx_timeseries (history), and no mention of caching or how often the ECB fixing updates.

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