Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cny_bgn

[PAID $0.002 USDC/call, x402, eip155:8453] Official CNY/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_cny_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 full burden and does well: it discloses the paid x402 invocation ($0.002 USDC on eip155:8453), the data provenance, the returned fields (rate date, method, source attribution), and the peg-vs-fixing branching. It stops short of describing failure behavior when no fixing exists or latency/caching characteristics.

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 front-load the payment/transport requirement then the data content, with no filler. The bracketed pricing prefix slightly interrupts the core purpose statement, but overall it is dense and earns its length.

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, the description must explain what comes back, and it does: rate, rate date, derivation method, and attribution. Missing are error/no-fixing behavior and any note on update frequency, which would be needed for an agent to reason about staleness.

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?

There are zero input parameters, so there is no parameter meaning to add; the baseline of 4 applies. The description instead spends its space on output and provenance semantics, which is the right allocation.

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 the exact resource (CNY/BGN reference rate), the authoritative source (European Central Bank fixing), and the fallback semantics (official peg when BGN is pegged). The currency pair in the name plus this description makes it unambiguous against the hundreds of fx_* siblings, which are differentiated only by the pair.

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 appropriate usage through 'Deterministic, sourced, no estimate', which signals this is for authoritative reference rates rather than indicative quotes, but it never names an alternative or exclusion (e.g. fx_convert for conversion, fx_timeseries for history, fx_latest for a snapshot). Guidance is inferable but not stated.

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