Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_idr_cad

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does well on sourcing: it discloses the payment model ($0.002 USDC per call, x402, eip155:8453), the data source, the derivation method (direct, cross via EUR, peg-derived), the accompanying rate date and attribution, and that the value is deterministic rather than estimated. It stops short of stating freshness/update cadence, caching behavior, or failure modes when no fixing exists.

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 plus a bracketed cost prefix; every clause (source, method, date, attribution, determinism) earns its place. The payment tag is placed ahead of the purpose, which slightly delays the core statement of what the tool returns.

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 rate tool with no output schema, the description gives source, derivation method, date and attribution, which covers most of what an agent needs. Because there is no output schema, a brief indication of the response shape (field names for rate/date/method) would have closed the remaining gap.

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 about input semantics to document. The description correctly focuses on what the fixed pair returns rather than inventing parameter detail.

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 (the official IDR/CAD reference rate) and its provenance (European Central Bank fixing, or the official peg), which is exactly what an agent needs to know it is a single-pair spot rate. It does not, however, state quote direction (IDR base vs CAD base), which is the main ambiguity against the hundreds of sibling fx_* pair tools and fx_convert.

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 name; there is no explicit when-to-use, when-not, or pointer to alternatives such as fx_convert or fx_timeseries. The one piece of decision-relevant guidance present is the price/x402 disclosure, which lets an agent weigh cost before calling.

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