Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cny_bhd

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does substantial work: it discloses the cost ($0.002 USDC/call), the payment protocol and chain (x402, eip155:8453), the authoritative source (ECB fixing / official peg), the derivation method, and a determinism guarantee ('no estimate'). The main omission is failure behavior — nothing says what happens when no fixing exists or the rate is stale.

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?

A single dense sentence that front-loads the billing tag so an agent can make a cost decision before reading further, then states purpose, source, and output fields in that order. No filler, nothing repeated from the (empty) schema.

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 parameters, no annotations, and no output schema, the description must describe the return shape itself, and it does — rate, rate date, method (direct/cross via EUR/peg-derived), and source attribution. What it lacks is edge-case guidance on unavailable fixings or staleness, the one gap for a paid data-lookup tool.

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 parameter meaning to convey and the baseline of 4 applies. The description correctly spends its words on return-value semantics instead.

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?

States a specific verb+resource ('Official CNY/BHD reference rate') and pins down the data source (latest ECB fixing, or the official peg when BHD is pegged). Because the pair is encoded in both the name and the sentence, an agent can distinguish it from the ~400 other fx_* siblings without opening a 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 — fetch this when you need the current CNY/BHD reference rate — but there is no explicit routing to the obvious alternatives in this crowded family, notably fx_convert (for converting an amount) or fx_timeseries (for historical rates). With hundreds of near-identical siblings, missing that differentiation leaves real inference work to the agent.

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