Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_czk_gbp

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full load, and it does disclose genuinely useful behavior: paid access at $0.002 USDC/call via x402 on eip155:8453, ECB as the authoritative source, peg-derived fallback, and 'deterministic, no estimate' data-quality guarantees. However, it omits operational behavior an agent needs — freshness cadence (daily fixing, no publication on TARGET holidays), what happens when no fixing exists, and caching/retry behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A price/payment tag followed by one dense sentence — purpose, source, fallback rule, returned fields, and data-quality claim, all front-loaded with zero filler. Nothing could be removed without losing information.

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, no-output-schema lookup tool, the description supplies most of what an agent needs: cost, payment protocol, data source, fallback semantics, and the nature of the returned values. The main remaining gap is freshness/holiday behavior, which matters for a fixing-based rate but is a narrow omission.

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 the baseline of 4 applies. The description goes slightly beyond by naming what the response carries (rate date, method, source attribution) even though no output schema exists, though it does not specify numeric precision or response format.

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 combination: the official CZK/GBP reference rate, sourced from the latest ECB fixing, with peg fallback noted. Within a sibling set of hundreds of near-identical fx_XXX_YYY pairs, the description establishes what makes this particular pair tool authoritative (ECB fixing, peg handling) rather than a generic quote.

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: 'latest ... fixing' signals a point-in-time reference rate rather than an amount conversion. There is no explicit statement of when to prefer this over fx_convert (converting amounts), fx_timeseries (historical), or fx_latest (multi-pair), which matters given the very large sibling family.

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