Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xof_bgn

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

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?

With no annotations, the description carries the full burden and does well: it discloses a metered cost ($0.002 USDC per call, x402, eip155:8453), guarantees determinism and sourcing with 'no estimate', and explains that pegged currencies return the official peg and that the method used is reported. It does not mention rate limits, failure modes, or staleness/fallback behavior when no fresh fixing exists.

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 plus a short qualifier. The cost/access tag is front-loaded so the agent sees the payment requirement first, and every clause (date, method, attribution, peg handling) adds information rather than repeating the name.

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 it explains what is returned (rate, rate date, derivation method, source attribution) and the peg edge case. The one notable gap is quote direction: it never says whether the value is BGN per XOF or XOF per BGN, which matters for a pair-named FX 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 nothing for the description to disambiguate beyond confirming the pair is fixed by the tool itself. The description correctly adds no parameter noise.

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 (XOF/BGN reference rate) and a specific provenance (official ECB fixing, or the official peg when BGN is pegged), which is exactly what distinguishes this tool from the hundreds of sibling fx_<base>_<quote> tools and from fx_convert/fx_latest.

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?

It implies usage (get the authoritative single-pair rate rather than an estimate) but never states when to pick this over fx_convert, fx_latest or fx_timeseries, nor any preconditions. For a no-parameter tool the routing decision is almost entirely on the agent to infer.

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