Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_czk_sek

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

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 carries the full burden and does disclose the paid access model ($0.002 USDC per call, x402, eip155:8453) plus the determinism and sourcing guarantees. What it omits is failure behavior — e.g. what is returned on weekends/holidays when no fixing exists, or whether a stale date is served.

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 dense sentence, front-loaded with the price tag and then the purpose, rate-date, and method details. Every clause is informative, though the bracketed payment metadata slightly competes with the core purpose for the reader's first attention.

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 single-value lookup with no output schema and no annotations, the description covers the source, the resolution method (direct, cross via EUR, peg-derived), and the returned metadata well enough to call it correctly. Only edge-case behavior around missing fixings remains unaddressed.

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 beyond the pair encoded in the name. The baseline for a parameterless tool applies, with no compensating gap to fill.

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?

The description names a specific resource and scope: the official CZK/SEK reference rate from the ECB's latest fixing, including the peg fallback. The pair is unambiguous and it explicitly says this is a sourced, deterministic fixing rather than an estimate, which is exactly what distinguishes it from a generic conversion tool like 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?

Usage is only implied by the pair-specific name; there is no statement of when to prefer this over fx_convert, fx_latest, or fx_timeseries, nor any note about requiring payment or a funded x402 wallet. The one useful constraint is the 'no estimate' guarantee, which signals it should not be used where interpolated or real-time rates are expected.

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