Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_bgn_jpy

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

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 supplied, the description carries the full burden and does well: it discloses the paid x402 cost ($0.002 USDC/call on eip155:8453), the upstream source (ECB), the derivation method (direct, cross via EUR, or peg-derived), determinism, and that no estimation occurs. It stops short of stating behavior on non-publishing days (ECB holidays/weekends) or how the most recent fixing is selected, which matters for a 'latest' rate.

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 with no filler, though the bracketed pricing/x402/eip155 preamble precedes the actual purpose, delaying slightly the answer to 'what does this do'. Moving the rate definition first and the payment terms last would front-load better.

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, output-schema-less tool the description covers the essentials: instrument, source, method, vintage (rate date), determinism and cost. The remaining gap is freshness semantics — the ECB publishes only on business days, and the description does not say what 'latest' resolves to on a weekend or holiday, which is the main thing an agent could get wrong.

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 the schema requires no explanation and the baseline applies. The description still adds value by enumerating what the returned record identifies (rate date, method, source attribution), which frames the output rather than repeating an empty schema.

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?

Names the exact resource (BGN/JPY reference rate), the specific verb/operation (retrieve latest ECB fixing), and the fallback case (official peg when JPY is pegged). Among hundreds of fx_* siblings, the pair is unambiguously fixed by the tool name and restated in prose, so an agent can distinguish it from fx_bgn_eur or fx_usd_jpy 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 by the fixed pair and 'latest ECB fixing', which signals a current spot reference rather than a conversion or history lookup. However, it never names alternatives such as fx_convert (arbitrary amount conversion), fx_timeseries (historical series) or fx_latest, nor does it state when not to use this tool.

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