Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sar_thb

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

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 does substantial work: it discloses the price ($0.002 USDC/call), the payment protocol (x402), the chain (eip155:8453), and that the value is a deterministic sourced fixing rather than an estimate. It does not describe payment-failure behavior, auth flow, or update cadence, so it stops short of full transparency.

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 with the paid-endpoint metadata front-loaded, followed by what the value is and how it is derived. Every clause carries information; only the closing 'Deterministic, sourced, no estimate' slightly restates the attribution claim made earlier.

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 supplies the return semantics an agent needs: the rate, the rate date, the derivation method (direct, cross via EUR, or peg-derived), and source attribution. The main gap is freshness/update cadence and routing guidance against fx_latest/fx_timeseries.

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 and the baseline of 4 applies. The pair is fixed by the tool identity itself, which the description confirms.

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 pair: 'Official SAR/THB reference rate: latest European Central Bank fixing'. The currency pair is unambiguous and matches the tool name exactly, and it names the exact data source (ECB fixing) so an agent knows this is a spot reference rate for this one pair, not a conversion helper.

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: 'latest ... fixing' scopes it to the current spot rate, implicitly excluding historical/time-series use. However, with hundreds of siblings including fx_latest, fx_timeseries, fx_convert and the inverse fx_thb_sar, the description names no alternative and gives no condition for choosing between them.

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