Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_eur_sgd

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 discloses the critical trait: a paid call at $0.002 USDC via x402 on eip155:8453, plus determinism and no-estimation guarantees. It stops short of stating update cadence or what happens when no fixing exists for a date.

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?

Two sentences with no filler, front-loading the payment requirement before the capability. Leading with billing metadata rather than the resource is slightly awkward but serves the agent's cost decision.

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 and no annotations, the description still names the returned components (rate, rate date, derivation method, source attribution), which is what an agent needs to trust the value. Missing only the freshness/update policy and error behavior for unavailable fixings.

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 schema is empty and takes zero parameters, so there is nothing for the description to disambiguate. Baseline applies; no parameter information is missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: the official EUR/SGD reference rate, sourced to the ECB fixing or the official peg. The pair is unambiguous and the scope (single latest fixing, not a series) is explicit, so an agent can distinguish it from conversion or timeseries siblings.

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?

Implies usage via 'no estimate' and 'reference rate', suggesting it is for authoritative lookups rather than conversions, but it never names fx_convert, fx_latest, or fx_timeseries as alternatives, nor states when not to use it.

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