Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cad_idr

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses the x402 micropayment requirement ($0.002 USDC per call on eip155:8453), the data provenance, and the resolution method (direct, cross via EUR, or peg-derived). It also asserts determinism and no estimation, which is meaningful behavioral context. It stops short of covering error/staleness behavior when a fixing is unavailable.

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 front-loaded sentence: cost and payment rail in brackets, then the resource, then the return contents. Efficient, though the closing triad 'Deterministic, sourced, no estimate' is mildly redundant and could be tightened.

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

Completeness5/5

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

For a zero-parameter lookup with no output schema, the description supplies everything an agent needs: what is returned (rate, rate date, derivation method, source attribution), how it is obtained, and what it costs. Nothing material is missing for correct invocation.

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 beyond confirming that the currency pair is fixed by the tool itself. The description makes that implicit contract clear and adds the output attributes (rate date, method, source) that a caller would otherwise have to discover.

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 the exact resource (CAD/IDR), the authority behind it (European Central Bank fixing, or the official peg when IDR is pegged), and the retrieval scope ('latest'). That is enough to distinguish it from siblings like fx_timeseries or fx_convert, though those alternatives are never named, so differentiation is inferred from the fx_<base>_<quote> naming convention rather than stated.

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: 'latest' signals this is a spot-lookup tool, not a historical series, and 'no estimate' signals it is preferred over modelled rates. There is no explicit statement of when to choose it over fx_convert for amount conversion or fx_timeseries for history, and no preconditions 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