Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_pln_kmf

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses the paid x402 model at $0.002 USDC per call on eip155:8453, the upstream source (ECB), the fallback behavior for pegged currencies, and the determinism guarantee ('no estimate'). It stops short of error behavior, freshness/staleness limits, or rate limits, so it is strong but not complete.

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?

Two sentences and a bracketed cost tag; the pair, source, fallback and guarantees are all front-loaded with no filler. Nothing could be removed without losing information an agent needs before paying for the call.

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?

There is no output schema, and the description compensates by enumerating what the response carries: the rate, the rate date, the derivation method (direct, cross via EUR, peg-derived) and source attribution. Only pricing/payment mechanics on failure and data staleness are left unstated, minor for a zero-parameter rate lookup.

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 schema has nothing to explain and the baseline is a 4. The description correctly implies the call is fully parameterless by specifying both currencies in the tool identity itself.

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?

The description names a specific resource ('Official PLN/KMF reference rate'), its source ('latest European Central Bank fixing'), and its fallback ('official peg when KMF is pegged'). This is enough for an agent to distinguish this pair-specific rate tool from generic siblings like fx_latest or fx_convert without opening a 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 only implied: 'Official... no estimate' signals this is the authoritative reference rate rather than an estimate, which softly steers an agent away from approximation tools. But it never states when to prefer it over fx_latest, fx_convert, or fx_timeseries, and there are no explicit exclusions or prerequisites beyond the payment note.

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