Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_idr_sar

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

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 burden and does real work: it discloses a paid access model ($0.002 USDC/call, x402, eip155:8453), the upstream authority (ECB), the derivation method (direct, cross via EUR, or peg-derived), and that results are deterministic/sourced with no estimation. Missing only rate-limit, caching/freshness window, and failure behavior on unpaid calls.

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/pricing tag, then the resource, then the returned fields. Every clause carries information (source, date, method, attribution). The bracketed metadata is slightly noisy at the very front but appropriate for a paywalled tool.

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, no-output-schema tool, the description compensates well by enumerating what comes back: rate date, method, and source attribution. Remaining gap is the exact response field shape and the payment handshake, but the essential call-time context is present.

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?

Zero input parameters, so the baseline is 4. The description adds nothing parameter-related, but nothing is needed — the currency pair is fixed by the tool name and no arguments exist to misinterpret.

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 verb+resource: the "Official IDR/SAR reference rate" sourced from the "latest European Central Bank fixing" (or the official peg). It distinguishes itself from time-series and conversion siblings by emphasizing "latest" and "fixing". It does not explicitly address the inverse-direction sibling fx_sar_idr, so direction is left to the name alone.

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 for point-in-time spot reference rates, not conversions or historical series. However, no sibling is named (fx_convert, fx_timeseries, fx_latest, fx_sar_idr) and there is no explicit when-not-to-use guidance, which matters in a family of hundreds of near-identical fx_* tools.

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