Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sar_bhd

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 price and payment mechanism ($0.002 USDC/call via x402 on eip155:8453), the data provenance (ECB fixing, or peg-derived), and the guarantee of no estimation. It omits failure behavior, staleness handling, or rate limits, which keeps it short of a 5.

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 dense sentences with no filler, and the core purpose comes immediately after the pricing prefix. The cost/x402 preamble occupies the most valuable front-loaded position, which is slightly suboptimal for tool selection but contains information not available elsewhere.

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, so the description usefully enumerates what comes back (rate, rate date, method as direct/cross-via-EUR/peg-derived, and source attribution). That covers nearly everything needed to invoke and interpret a zero-parameter rate tool; only error or staleness behavior is left unspecified.

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 there is no schema semantics to explain and the baseline is 4. The description correctly spends no words on inputs and instead uses the space to describe the returned fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and direction ("Official SAR/BHD reference rate") plus the exact source ("latest European Central Bank fixing") and fallback ("official peg when BHD is pegged"). An agent can distinguish this from the hundreds of other fx_* pair siblings without opening any schema.

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 data-quality qualifiers ("Deterministic, sourced, no estimate"), which suggest it is the right choice when an exact official reference rate is needed rather than an approximate conversion. However, it never names alternatives such as fx_latest, fx_convert or fx_timeseries, and gives no explicit when-not-to-use condition.

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