Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xaf_idr

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

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?

No annotations are supplied, so the description carries the full burden, and it does well: it discloses the paid model ($0.002 USDC/call, x402, eip155:8453), the data source (ECB fixing, or official peg), and determinism/no estimation. It stops short of stating freshness cadence, failure behavior, or rate-limit characteristics.

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 with no filler, but the bracketed payment metadata is front-loaded ahead of the actual purpose, which delays the agent's answer to 'what does this do?' Moving the rate description first would improve scanning.

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?

With no output schema, the description usefully enumerates what comes back: rate, rate date, method (direct/cross via EUR/peg-derived), and source attribution. That covers the essential return contract for a zero-parameter lookup; only staleness or error behavior is missing.

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; there is nothing for the description to disambiguate. The pair is fixed in the tool name and restated in the description, which is sufficient.

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 (XAF/IDR) and a specific verb-like outcome ('Official XAF/IDR reference rate: latest ECB fixing'), plus the fallback case for a pegged IDR. It does not explain how it differs from generic siblings such as fx_convert, fx_latest, or fx_timeseries, so an agent must infer the distinction from the pair-specific tool name.

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 reference rate' and 'no estimate' hint that this is the authoritative fixing rather than a conversion or time series, but the description never names an alternative or states when not to use it. With hundreds of fx_* siblings, explicit routing guidance would have been valuable.

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