Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sgd_usd

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

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 well: it discloses the payment requirement and mechanism ($0.002 USDC/call, x402, eip155:8453), the data provenance (ECB fixing), the fallback behavior when USD is pegged (peg-derived rate), and that the value is deterministic with no estimation. It stops short of stating what happens on weekends/holidays when the ECB does not publish, which is the main behavioral gap for a fixing-based tool.

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 compact sentences, front-loaded with the payment/metering prefix so the cost is visible before any commitment, then the substantive purpose and provenance. Slightly dense with parentheticals, but every clause (date, method, attribution, no-estimate) carries information.

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?

No output schema exists, and the description compensates by enumerating what comes back — rate date, derivation method (direct, cross via EUR, peg-derived), and source attribution. What remains unstated is quotation convention (SGD per USD vs USD per SGD) and numeric precision, minor but relevant for a rate tool.

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 and the schema is empty, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The description instead usefully characterizes the response fields (rate date, method, source attribution).

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?

Names a specific resource (the SGD/USD rate) and pins down exactly which rate it is — the ECB reference fixing, or the official peg when USD is pegged — rather than a generic market quote. It does not name a sibling such as fx_convert or fx_latest to differentiate scope, but the pair is unambiguous from the name and description together.

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 context is implied rather than stated: 'Official ... reference rate', 'Deterministic, sourced, no estimate' signals this is for cases needing audit-grade official figures rather than quick conversion. There is no explicit 'use fx_convert instead for arbitrary pairs' or guidance on when a la carte per-pair calls beat a conversion tool, so the agent must infer the routing.

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