Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_huf_gbp

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

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 carries the full burden and does notably well: it discloses the paid cost and payment rail ($0.002 USDC, x402, eip155:8453), the authoritative source, the deterministic/no-estimate guarantee, and the derivation method variants. It stops short of stating staleness behavior, whether non-business days return the prior fixing, or error behavior for unsupported pairs.

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?

Effectively two sentences with no filler, and the core resource statement comes first after the payment tag. The bracketed pricing prefix is front-loaded and useful for an agent deciding whether to spend, though it slightly delays the semantic payload.

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?

There is no output schema, and the description compensates by naming the returned fields (rate date, method, source attribution) plus the determinism guarantee. For a zero-parameter single-value lookup that is close to complete; only staleness/holiday semantics and the numeric precision/quoting convention are 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?

The tool takes zero parameters, so there is nothing to disambiguate; baseline 4 applies. Notably, the description does clarify that the pair direction is baked into the tool name rather than passed as an argument, which is the only semantic question a zero-param tool raises.

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 names a specific resource (HUF/GBP reference rate), a specific authoritative source (European Central Bank fixing), and the fallback case (official peg when GBP is pegged). That is far more than the self-describing name alone. It does not explicitly distinguish itself from siblings like fx_latest, fx_convert, or fx_timeseries, which is why it lands at 4 rather than 5.

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 implied rather than stated: 'latest ECB fixing' and 'no estimate' tell an agent this is a spot reference value, not a forecast or a conversion. However, nothing says when to pick this over fx_latest, fx_convert, or fx_timeseries, and there are no exclusions or freshness caveats (weekends, holidays, publication time), so the agent must infer the routing.

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