Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_nzd_gbp

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With zero annotations the description carries the full burden and does well: it discloses the paid model ($0.002 USDC/call, x402, eip155:8453), the authority (ECB) and methodology (direct, cross via EUR, or peg-derived), and asserts determinism with no estimation. What it omits is operational behavior such as payment precondition/failure handling and publication cadence or staleness of the latest fixing.

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?

One tight sentence with no filler; the pricing/x402 bracketed prefix is a marketplace convention, and the substantive purpose follows immediately. It is dense but every clause contributes (source, fallback, method, date, attribution), with only mild compression cost in readability.

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 tool with no output schema, the description covers most of what an agent needs: what the value represents, its provenance, the resolution method, and that a rate date and attribution accompany it. It stops short of stating quote convention/units (GBP per NZD) and how fresh the 'latest' fixing can be during market closures.

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 schema has zero parameters at 100% coverage, which sets a baseline of 4. The description reinforces this by making clear the pair and source are fixed at the tool level, so an agent knows no inputs are required and no amount/date/base-currency arguments exist.

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 names a specific verb+resource: the 'Official NZD/GBP reference rate', specifically the 'latest European Central Bank fixing', and clarifies the peg fallback. It is unambiguous which currency pair and which data source, though it never explicitly distinguishes itself from adjacent siblings such as fx_convert, fx_timeseries, or the other fx_* pair tools.

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: an agent can infer this is the tool to call for a spot NZD/GBP reference rate. There is no explicit when-to-use statement, no exclusions (e.g. 'use fx_timeseries for historical data' or 'use fx_convert for conversion arithmetic'), and no guidance on what to do if the fixing is stale over a weekend or holiday.

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