Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_usd_bhd

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description discloses the per-call price, x402 payment requirement and network, data source and fallback methodology, determinism, and absence of estimation. It also explains that the result carries a rate date, calculation method, and source attribution, providing strong insight into how the answer is produced.

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?

The payment prefix surfaces cost and settlement details immediately, followed by the purpose, methodology, returned metadata, and reliability characteristics in two compact statements. The wording is dense but appropriately sized, with almost no expendable content.

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-argument tool without an output schema, it covers the pair, reference-rate semantics, provenance, derivation methods, returned metadata, and payment cost. It could still clarify quote units explicitly as BHD per USD, state the publication or freshness cadence, and distinguish the generic FX alternatives.

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?

There are no parameters, so the baseline is 4 and no argument syntax needs explanation. The fixed pair and latest-rate wording reinforce that this is a zero-argument lookup rather than a configurable currency conversion.

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 precisely identifies the fixed USD/BHD pair, its official reference-rate nature, latest-rate scope, and possible direct, EUR-cross, or peg-derived calculation. It does not explicitly contrast itself with the generic or inverse FX siblings, so sibling differentiation remains implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

“Latest” official reference rate and “no estimate” establish a clear context for choosing this tool when a sourced current fixing is required. However, it does not explicitly route conversion, historical, or inverse-pair requests to fx_convert, fx_timeseries, or fx_bhd_usd.

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