Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_chf_bhd

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

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?

No annotations are supplied, so the description carries the full burden and does well: it discloses the paid x402 model ($0.002 USDC/call, eip155:8453), the upstream source (ECB), the fallback path (official peg), and that results are deterministic and not estimated. What it omits is update cadence and failure behavior if no fixing is available for the pair.

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 tight sentences, front-loaded with the cost/access model followed by the data semantics. Every clause adds information; the pricing tag is slightly noisy but legitimately useful for an x402 paid call.

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, yet the description still enumerates the returned fields (rate, rate date, derivation method, source attribution), which is exactly what an agent needs to trust the value. Complete for a zero-parameter single-value lookup; only cadence and edge-case behavior remain undocumented.

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 the baseline is 4. The description correctly implies a parameterless call and instead spends its words on what the response contains, which is the right use of the budget.

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?

States a specific verb+resource: the official CHF/BHD reference rate, naming the exact source (ECB fixing) and the peg fallback. The pair is unambiguous and matches the tool name. It does not, however, distinguish itself from siblings like fx_convert, fx_latest, or fx_timeseries, which an agent could plausibly reach for instead.

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 by the pair name and the 'reference rate' framing, so an agent knows this is a single-pair spot lookup. But there is no explicit guidance on when to prefer fx_convert (arbitrary conversion) or fx_timeseries (historical), nor any exclusion about what this tool will not do.

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