Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_isk_xof

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 disclosure burden and does meaningful work: it states the cost and payment protocol (PAID $0.002 USDC/call, x402, eip155:8453), the provenance (ECB fixing with source attribution), the derivation method (direct, cross via EUR, or peg-derived), and the guarantee of being deterministic and non-estimated. The main omission is whether a failed or stale fixing produces an error versus a fallback value.

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 dense sentences with no filler; each clause adds a distinct fact (price, source, method, determinism). The bracketed payment tag is front-loaded, which is useful but slightly competes with the purpose statement as the opening hook.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 everything an agent needs: which pair, which authority, which derivation method, what metadata accompanies the number, and that the result is not an estimate. Nothing material is missing for correct invocation.

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 there is nothing for the description to disambiguate beyond confirming that the currency pair is fixed by the tool identity rather than supplied as input. Baseline 4 applies for a parameterless tool.

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 the exact resource and scope: the official ISK/XOF reference rate from the latest ECB fixing, or the official peg when XOF is pegged. That is a specific verb-and-resource statement that separates it from fx_convert, fx_latest and fx_timeseries. It stops short of explicitly naming those siblings as alternatives, which keeps it out of 5 territory.

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 rather than stated: the agent can infer this returns a single official reference rate for one currency pair, so it is the right choice when a sourced ISK/XOF fixing is needed. There is no explicit when-not guidance, no pointer to fx_convert for arbitrary amounts or to fx_timeseries for historical series, so the routing decision is left to inference despite the huge sibling set.

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