Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_usd_huf

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description itself discloses the $0.002 USDC per-call cost, x402 payment mechanism, eip155:8453 network, deterministic behavior, and absence of estimation. It also explains the direct, EUR-cross, and peg-derived methods and promises rate-date and source attribution, providing strong payment and provenance transparency.

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 payment requirement is front-loaded, and the remaining text compactly covers scope, source, fallback, methods, and result metadata. The main sentence is dense, and 'Deterministic, sourced, no estimate' partly repeats the official-fixing and source-attribution language.

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 an output schema, it covers the essential result contents, source and fallback behavior, determinism, and payment details. It would be more complete with explicit routing for history or conversion requests and clarification of quote orientation or fixing behavior on non-publication days.

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?

There are no parameters, so the zero-input baseline applies and there is no undocumented argument burden. The fixed USD/HUF pair and latest-rate scope reinforce that no date, amount, or currency selection is needed.

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 identifies the exact resource and operation: providing the latest official USD/HUF reference rate, using an ECB fixing or an official-peg fallback. The emphasis on a latest, sourced reference rate with 'no estimate' distinguishes it from conversion, historical-series, and estimated-rate tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'latest' reference-rate framing and 'no estimate' statement establish a clear use case: obtaining a current, authoritative USD/HUF quote. It does not explicitly direct historical requests to fx_timeseries or amount conversions to fx_convert, so it lacks full when-not and alternative-tool guidance.

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