Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_gbp_huf

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

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?

No annotations exist, so the description carries the full burden and does a lot: it discloses the paid cost ($0.002 USDC/call), the x402 payment scheme, the chain (eip155:8453), the authoritative data source, the peg fallback behavior, and that values are deterministic rather than estimated. What is missing is freshness cadence (how often the fixing updates) and what a caller must do to satisfy the x402 payment.

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?

Two sentences, front-loaded with the payment/transport tag so cost is known before commitment, then the data guarantee. The bracketed prefix is information-dense rather than wasteful, though it competes with the actual purpose for the first read.

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, the description supplies cost, payment protocol, source, method variants and the shape of the returned record. Only update frequency and the mechanics of paying via x402 are left unstated.

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?

Zero parameters, so no parameter semantics are required; baseline is 4. The description instead characterizes the response fields (rate date, method, source attribution), which is useful given there is no output schema.

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 resource (GBP/HUF reference rate) plus its provenance (ECB fixing, peg handling) and derivation method (direct, cross via EUR, peg-derived). An agent can distinguish this from fx_latest, fx_timeseries or fx_convert without opening any schema.

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?

Use is implied by 'latest ... fixing' for a current spot rate, but the description never names alternatives (fx_convert for amounts, fx_timeseries for history, other fx_* pairs) nor states exclusions. Guidance is inferable rather than explicit.

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