Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_pln_xof

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 payment requirement ($0.002 USDC, x402, eip155:8453), the upstream source (ECB), the derivation method (direct, cross via EUR, peg-derived), and the guarantee that values are deterministic and never estimated. It stops short of describing the response shape or field names, which matters since there is no output schema.

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 compact clauses cover payment terms and data semantics with no filler, and the resource identity is front-loaded after the billing tag. The bracketed payment prefix is useful but slightly crowds the front of the sentence, pushing the actual purpose to second position.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-output-schema tool, the description covers source, method, dating, and cost. The gap is the quote convention: it never says whether the rate is PLN per XOF or XOF per PLN, nor the numeric precision or response field names, which an agent must know to use the value correctly.

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 no parameter semantics to explain and the baseline applies. The description correctly makes no parameter claims.

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?

Names the exact resource and pair ('Official PLN/XOF reference rate') and specifies the value returned: the latest ECB fixing. Among hundreds of identically-shaped fx_* siblings, the pair is unambiguous from the name plus the description's restatement of source and method.

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?

The description implies when to use it (you need the PLN/XOF reference rate) but never states when to prefer a sibling such as fx_convert, fx_latest, or fx_timeseries, nor what to do when XOF is pegged versus floating beyond noting the method field. Usage is inferable from the pair name rather than guided.

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