Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_pln_aed

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 load and does well: it discloses the paid-per-call cost and payment scheme ('$0.002 USDC/call, x402, eip155:8453'), the authoritative source (ECB fixing), the peg fallback behavior when AED is pegged, and that results are deterministic and non-estimated. What it omits is failure behavior when no fixing exists and any freshness/caching guarantee.

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?

A single dense sentence, front-loaded with the payment cost then the substantive description. Every clause earns its place, though the bracketed payment prefix and semicolon-chained parenthetical make it slightly harder to scan than a split into two sentences would be.

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 source, derivation method, peg fallback and the fields returned (rate date, method, attribution) — enough for an agent to call it and interpret the result. Missing only error/absence handling and refresh cadence.

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 meaning to add; baseline applies. The description instead spends its space on return-field semantics (rate date, method, source attribution), which is the useful substitute here.

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?

States a specific resource and scope: 'Official PLN/AED reference rate: latest European Central Bank fixing'. The currency pair plus the named data source makes the operation unambiguous and distinguishes it from aggregate siblings like fx_latest or fx_timeseries. It never explicitly routes to alternatives, so it stops short of a 5.

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 by the pair in the name and the 'reference rate' framing. There is no statement of when to prefer this over fx_convert (conversion), fx_latest (multi-currency snapshot) or fx_timeseries (history), all of which sit in the sibling list and could plausibly be chosen for the same task.

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