Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_chf_gbp

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description discloses the exact $0.002 USDC per-call price, x402 payment mechanism, and eip155:8453 network, alongside deterministic, sourced, non-estimated behavior. It also explains the official-peg fallback, direct/EUR-cross/peg-derived methods, rate date, and attribution, providing substantial operational and data-provenance context.

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?

The compact description places cost and payment constraints first, then efficiently covers purpose, provenance, calculation methods, and determinism. Its technical notation is dense, but each element affects tool selection, payment, or interpretation.

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 tool without an output schema, it usefully identifies the expected rate date, method, and source attribution as well as the data basis and cost. It could be more complete by explaining fixing availability or staleness behavior and explicitly routing users to the generic conversion, latest-rate, or timeseries siblings when appropriate.

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 has zero parameters, so the baseline score of 4 applies and no argument documentation is necessary. Fixing the currency pair and latest-rate scope in the description reinforces why invocation requires no user inputs.

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 clearly identifies an official CHF/GBP reference rate, its latest-fixing scope, ECB source, and accompanying date, method, and attribution. It does not explicitly distinguish this fixed-pair lookup from fx_convert, fx_latest, or fx_timeseries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrases "latest European Central Bank fixing" and "no estimate" provide useful context for choosing an authoritative reference fixing rather than an estimated value. There are no explicit when-not conditions or pointers to siblings for conversions, other currency pairs, or historical series.

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