Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cad_bgn

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

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 burden and does real work: it discloses the paid model ($0.002 USDC per call via x402 on eip155:8453), the provenance (ECB fixing or official peg), the derivation method (direct, cross via EUR, peg-derived), and that the value is deterministic and never estimated. It stops short of noting failure behavior on ECB non-publication days (weekends/holidays) or the response shape.

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 payment tag, with no filler. The payment/chain metadata is front-loaded ahead of the actual purpose, which slightly delays the core statement but is justified given the per-call cost.

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?

The tool is simple (no inputs, no output schema), and the description compensates by stating what the returned rate carries: rate date, derivation method, and source attribution. Only edge-case behavior (ECB holiday gaps, precision) is left unstated, which is minor for a zero-parameter lookup.

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 to disambiguate and the baseline is 4. Nothing in the description misleads about inputs, and the pair is encoded in the tool name rather than a parameter.

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 an exact resource and scope: the official CAD/BGN reference rate, sourced to the ECB fixing or the official peg. Combined with the name, an agent can tell instantly which of the hundreds of fx_<base>_<quote> siblings this covers and what rate it returns.

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: the word "latest" bounds it to the current fixing and implicitly excludes historical series, and the pair is fixed by the name. There is no explicit routing to alternatives such as fx_cad_eur or fx_convert for amount conversion, nor any statement about when this pair is the right choice.

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