Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_chf_huf

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 well: it discloses the paid access model ($0.002 USDC/call via x402 on eip155:8453), the upstream source (ECB), determinism, the peg-handling branch for HUF, and the fields returned (rate date, derivation method, source attribution). It does not explain the payment/response mechanics of the x402 flow, but the substantive behavioral traits are covered.

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 single front-loaded sentence: pricing/payment metadata first, then the resource, source, and returned attributes. No filler, and the parenthetical about pegging is placed where it resolves the only real ambiguity.

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 covers cost, provenance, determinism, fallback behavior, and the semantic content of the result. It stops short of describing the response envelope or units/quoting convention, which would matter for a downstream consumer, but nothing needed to decide to call it is missing.

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 makes clear the pair and source are fixed by the tool itself, so there is no ambiguity about what inputs would be needed.

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 specific resource and scope: the official CHF/HUF reference rate, latest ECB fixing (or peg fallback). That is more than the name conveys, since it pins the source and the notion of a 'reference rate' rather than a conversion. It does not explicitly contrast itself with siblings like fx_convert or fx_latest, so sibling differentiation is left largely to the pair-encoded tool name.

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: call this when you need the current CHF/HUF reference rate from an official source. 'Deterministic, sourced, no estimate' hints at when-not (don't use for projections), but no alternative tool such as fx_convert, fx_latest, or fx_timeseries is named or excluded. An agent must infer routing from the pair-specific name alone.

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