Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aud_pln

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations present, the description carries the full behavioral burden. It does disclose the paid model ($0.002 USDC per call, x402, eip155:8453) and the determinism/no-estimate property. But it omits what happens when no fixing exists for a date, whether any authentication or wallet setup is needed beyond x402, and error or caching behavior, which are material for a paid tool.

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?

One compact sentence that front-loads the pricing/protocol bracket and then the purpose. Every clause carries information (rate, source, date, method, attribution, determinism). The only cost is that the price prefix precedes the actual purpose, slightly delaying what the tool does.

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?

There is no output schema, no annotations, and no parameters, so the description must cover everything. It helpfully enumerates the returned fields (rate date, method of derivation, source attribution), which compensates for the missing output schema. However, it leaves open the paid-call mechanics and the no-fixing/error case, so it is not fully complete for a paid data tool.

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 and the baseline of 4 applies. The currency pair is fixed by the tool identity, so no input meaning is lost.

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 a specific resource (official AUD/PLN reference rate) and pins down its provenance (European Central Bank fixing) plus the fallback case (official peg). That is far more specific than the bare name, though it never names a sibling tool such as fx_convert or fx_latest to distinguish when a plain pair lookup is preferable to a conversion or a time series.

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: an agent can infer this is the tool for an authoritative AUD-to-PLN spot reference. There is no explicit when-to-use versus when-not, no mention of fx_convert for amount conversion, and no guidance on what to expect on non-publishing days (weekends/TARGET holidays).

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