Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_bgn_xof

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

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 supplied, the description carries the full burden and does well: it discloses the price and payment protocol ($0.002 USDC/call, x402, eip155:8453), the data source (ECB fixing or official peg), the resolution method (direct, cross via EUR, peg-derived), and that results are deterministic with no estimation. It does not mention staleness limits, rate-limit or failure behavior on non-trading days, which keeps it below 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?

One tight passage with no filler, and the key noun phrase (BGN/XOF reference rate) appears early. The payment/billing prefix leads the text, which is mildly front-loaded with commercial rather than task information, but it is short and legitimately actionable for an agent that must pay.

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-argument, single-value lookup with no output schema, the description covers the essentials: source, method, returned metadata (rate date, method, attribution), and determinism. An agent could call this correctly without further information, though it lacks any note on freshness cadence or what a missing fixing returns.

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 at the input layer; the baseline for a no-param tool applies. The description instead spends its space on what the fixed output contains, which is the right allocation.

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?

The description names a specific resource — the official BGN/XOF reference rate — and states its provenance (ECB fixing or official peg). It is clearly distinguishable from non-FX siblings, though it does not explicitly distinguish itself from fx_convert, fx_latest, or fx_timeseries, which also touch rates.

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: an agent wanting the BGN/XOF rate should call this. But there is no explicit guidance on when to prefer it over fx_convert (conversion) or fx_timeseries (history), and no statement of what happens for other pairs. The only concrete routing hint is the price, which signals a paid call.

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