Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_czk_eur

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

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 still discloses unusually useful behavior: a $0.002 USDC charge per call, x402 payment on eip155:8453, deterministic results, source attribution, and no estimation. It does not explicitly confirm read-only behavior or explain payment failures, data freshness around non-fixing days, or other error behavior.

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 paid-call prefix and two compact sentences pack in cost, scope, provenance, and output metadata without substantial repetition. The acronym-heavy payment prefix and generic parentheticals about pegs and cross-rate methods are somewhat dense and less relevant to this specific CZK/EUR lookup.

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 annotations or an output schema, the description covers the essential source, recency, returned metadata, determinism, and payment requirements. It could still clarify the numeric quote direction, freshness behavior when no new fixing exists, and how this tool differs from the generic FX siblings.

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 there are no argument semantics for the description to compensate for, meeting the baseline score of 4. The fixed currency pair and source scope further make clear that the caller does not configure the lookup.

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 precisely identifies the resource as the official CZK/EUR reference rate and narrows it to the latest European Central Bank fixing. It also promises the rate date, calculation method, and source attribution, although it does not explicitly distinguish this pair-specific lookup from siblings such as fx_latest or fx_convert.

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?

Phrases such as "latest European Central Bank fixing" and "no estimate" imply that this is appropriate when an agent needs the current official reference rate rather than an estimated value. However, there is no explicit when-to-use guidance or routing to fx_convert for amount conversion, fx_timeseries for history, or fx_latest for other latest-rate needs.

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