Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_bhd_gbp

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

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?

With no annotations, the description carries the full burden and does well: it discloses the price and payment rail ([PAID $0.002 USDC/call, x402, eip155:8453]), the authoritative source (ECB fixing, or official peg when pegged), the derivation method, and that results are deterministic and non-estimated. It omits edge-case behavior such as weekend/holiday fixings or staleness limits.

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?

A single dense sentence plus a bracketed cost prefix; every clause carries information (source, method, attribution, no-estimate guarantee). The price tag is front-loaded and useful for routing, though the body is slightly clause-heavy for one sentence.

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, payment protocol, data provenance, derivation method, and the fields returned, which is nearly everything an agent needs. The main residual gaps are staleness/holiday behavior and the numeric precision/format of the rate.

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 are no parameter semantics to explain; the baseline of 4 applies. The description compensates by describing what comes back (rate date, method, source attribution) even though there is no output schema.

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 resource (BHD/GBP) and a specific verb/content (official reference rate, latest ECB fixing) rather than a tautology. The pair is unambiguous from both name and description. It doesn't explicitly differentiate from siblings like fx_convert or fx_timeseries, though 'latest' and 'reference rate' implicitly do so.

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 only implied: an agent can infer 'call this to get the current BHD/GBP official rate'. There is no explicit statement of when to prefer it over fx_convert, fx_latest, or fx_timeseries, and no exclusions (e.g. 'not for historical dates'). The word 'latest' hints at a boundary but doesn't state one.

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