Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_isk_gbp

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 it does disclose the most important behavioral traits: a $0.002 USDC per-call x402 charge on eip155:8453, the underlying source (ECB fixing or official peg), deterministic non-estimated output, and the metadata returned (rate date, derivation method, attribution). It falls short only on failure behavior, e.g. what happens when no fixing is available or how stale a rate can be.

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 tight sentences plus a bracketed cost/auth tag, with the core statement front-loaded. The x402 chain identifier is arguably noise but is genuinely relevant to how the call is paid for, so it earns its place.

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 single-value lookup with no output schema, the description covers what is returned (rate, date, derivation method, attribution), how it is derived, and how it is paid for. Only resilience details (missing fixings, staleness, exact field names) are absent, which is a minor gap at this complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema-conformance baseline of 4 applies, but the description cannot add meaning to parameters that do not exist and says nothing about the implied fixed pair beyond the name. It is adequate rather than adding value.

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?

Names a specific resource and scope: the ISK/GBP official reference rate, sourced from the ECB fixing or official peg. That is precise enough to separate it from fx_convert (conversion) and fx_timeseries (history), but the description never names those siblings, so the differentiation is inferred rather than stated.

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: 'reference rate' and 'no estimate' signal this is for authoritative single-pair lookups rather than conversions or time series, but there is no explicit when-to-use or when-not-to-use statement and no pointer to an alternative tool. An agent must infer routing from the pair name and the word 'reference'.

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