Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xof_pln

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

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 substantial work: it discloses the price ($0.002 USDC/call), the payment protocol (x402, eip155:8453), the data provenance (ECB fixing vs official peg), the derivation method (direct, cross via EUR, or peg-derived), and that the value is deterministic and not an estimate. It stops short of covering failure modes, staleness windows, or rate limits, which keeps it off a 5.

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 sentences, front-loaded with the billing tag then the core purpose, with no filler. The bracketed payment prefix is dense but operationally necessary given that no annotations expose the cost.

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 no-param, no-output-schema lookup, the description covers the essentials an agent needs: what rate, from which source, by which method, with what date and attribution, and at what cost. It does not state the numeric precision or behavior when a fixing is unavailable, which is the only remaining gap.

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 the baseline is 4; the description correctly spends its words on the returned value instead of inventing inputs. It also clarifies the pair direction implicitly through the name and the 'XOF/PLN' phrasing.

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 a specific verb and resource — 'Official XOF/PLN reference rate: latest European Central Bank fixing' — with the exact currency pair, the issuing authority, and the fallback case (official peg). An agent can distinguish it from the hundreds of sibling fx_* pairs and from fx_convert/fx_timeseries without opening any schema.

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: 'latest ... fixing' signals a spot-rate lookup rather than historical or conversion use, which weakly separates it from fx_timeseries and fx_convert. However, no sibling is named and there is no explicit when-not guidance, so the agent must infer routing from the currency pair in the name.

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