Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_jpy_bhd

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/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 add real value: it discloses the paid cost ($0.002 USDC/call), the x402 payment scheme and eip155:8453 network, plus fallback behavior (peg-derived when BHD is pegged) and cross-rate methods. Gaps remain: nothing about failure modes when no fixing exists, freshness/caching, or whether the peg value is static.

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?

One well-packed sentence after the bracketed cost preamble; every clause (source, fallback, returned metadata, determinism) adds information. The price preamble is front-loaded and easy to scan, though the sentence is dense enough that the purpose arrives after the billing tag.

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?

With no output schema, the description must convey what comes back, and it does: rate date, method (direct/cross/peg-derived), and source attribution. For a zero-parameter lookup this is close to complete; only error/edge-case behavior and data freshness 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 the schema carries no semantic load and the baseline is 4. The description correctly implies a parameterless single-pair lookup with no currency or date inputs.

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-free but precise resource: the 'Official JPY/BHD reference rate' with the exact source ('latest European Central Bank fixing'). An agent can distinguish the pair and the source from the hundreds of sibling fx_* pair tools. It stops short of explicitly contrasting with fx_convert/fx_latest/fx_timeseries, but the resource is unambiguous.

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?

Implied usage is clear (fetch a single spot reference rate for JPY→BHD), and 'deterministic, sourced, no estimate' hints at when not to expect derived data. However, there is no explicit guidance on when to prefer fx_convert, fx_latest, fx_timeseries, or the inverse fx_bhd_jpy instead.

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