Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_gbp_sgd

[PAID $0.002 USDC/call, x402, eip155:8453] Official GBP/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_gbp_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?

With no annotations, the description carries the full burden and does well: it discloses the cost ($0.002 USDC per call), the payment protocol (x402, eip155:8453), the data source and attribution, the derivation method (direct, cross via EUR, or peg-derived), and the 'deterministic, sourced, no estimate' guarantee. It stops short of describing failure behavior when no fixing exists, caching, or the response envelope.

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 with the payment terms bracketed up front and the substance following immediately. Dense but not padded; the parenthetical method enumeration earns its place because it explains why results can differ from a naive cross rate.

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 and no annotations exist, so the description must supply everything, and it covers source, method, rate date, attribution, cost, and determinism. The main gap, with no output schema to lean on, is that the returned fields and their shape are not spelled out beyond 'rate date, method, source attribution'.

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. The baseline of 4 applies; the currency pair is fixed by the tool name and confirmed in the description.

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?

The description names the exact resource and scope: the 'Official GBP/SGD reference rate' from the 'latest European Central Bank fixing'. It goes further by stating the fallback case (official peg when SGD is pegged) and the derivation method, so an agent knows precisely what value it returns.

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: an agent can infer this is for the latest official reference rate rather than a live or intraday quote, and that it is not a general converter. It never explicitly contrasts with siblings such as fx_convert, fx_latest, or fx_timeseries, so the when-not-to-use case is left to inference.

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