Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aed_bhd

[PAID $0.002 USDC/call, x402, eip155:8453] Official AED/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_aed_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 a per-call charge ($0.002 USDC via x402 on eip155:8453), the upstream source (ECB), the fallback method chain (direct, cross via EUR, peg-derived), and that the result is deterministic with no estimation. It omits practical behavior such as caching/rate limits and what a payment failure looks like, 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 compact clauses, no filler, and every element (price, protocol, chain, source, method, determinism) carries information an agent needs. The bracketed payment metadata leads ahead of the actual purpose, which slightly delays the core statement, but it is arguably the most decision-relevant fact.

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 and no annotations, the description must cover both semantics and return shape, and it does: it names the fields returned (rate date, method, source attribution) and the pricing model. It does not specify the numeric precision, base/quote orientation of the rate, or weekend/holiday behavior for the ECB fixing, which are the remaining gaps.

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 nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The description adds the useful implicit constraint that the pair is fixed by the tool identity rather than passed in.

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 resource (AED/BHD reference rate) and its provenance (latest ECB fixing, or official peg for BHD), which is far more than a restatement of the name. An agent can tell exactly which currency pair and which rate type this returns 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?

The description implies usage (official reference rate for this specific pair) but never says when to prefer it over siblings such as fx_convert, fx_latest, or fx_timeseries, nor does it state exclusions or freshness expectations. The zero-parameter schema makes invocation unambiguous, but routing guidance is left to inference.

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