Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_huf_cad

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

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 at all, the description carries the full burden and does well: it discloses the paid access model ($0.002 USDC/call, x402, eip155:8453), the upstream authority (ECB), and the fact that the response carries rate date, derivation method, and source attribution. The main gap is what happens on non-publishing days (weekends/holidays) or when payment fails.

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?

Every sentence does work: the pricing/transport prefix comes first, then the resource definition, then provenance and determinism. It is a single dense block rather than fully front-loaded prose, but there is no filler.

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 tool, the description is nearly sufficient: it names the source, the derivation method, and the response fields, which is what an agent needs in lieu of an output schema. It only lacks edge-case behavior (stale fixings, errors, payment failure).

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, which is the baseline-4 case. The description correctly adds no parameter semantics because there are none, and instead explains what the parameterless call returns.

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 states a precise verb and resource: it returns the official HUF/CAD reference rate, specifically the latest ECB fixing or the official peg. An agent can immediately tell this is a single-pair FX lookup rather than a conversion or time-series tool. It stops short of a 5 because it never disambiguates direction against the inverse sibling fx_cad_huf or other related tools like fx_convert and fx_latest.

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 currency pair and the phrase 'no estimate', which hints at when a deterministic official fixing is preferred over an approximation. There is no explicit statement of when to choose this over fx_cad_huf, fx_convert, or fx_timeseries, and no mention of fallback behavior when the ECB has not published a fixing.

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