Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_thb_usd

[PAID $0.002 USDC/call, x402, eip155:8453] Official THB/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_thb_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 supplied, the description carries the full burden and does substantial work: it discloses a paid x402 endpoint at $0.002 USDC/call on eip155:8453, the data provenance (ECB fixing / official peg), the fallback logic when USD is pegged, and the guarantee that values are deterministic and non-estimated. Remaining gaps are freshness/staleness behavior and what happens if payment is not settled.

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 preceded by a bracketed pricing/transport header, front-loaded with the resource name. Every clause (source, peg fallback, method, attribution, determinism) adds information, though the sentence is long enough that the return-content list is slightly buried.

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?

There is no output schema, so the description must describe the return payload, and it does: rate, rate date, derivation method (direct, cross via EUR, or peg-derived), and source attribution. It is close to complete for a zero-parameter lookup; only numeric precision/units and staleness handling are left unstated.

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 description correctly frames this as a fixed currency-pair lookup requiring no inputs.

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 resource (THB/USD reference rate), its exact source (the latest European Central Bank fixing, or the official peg when USD is pegged), and what accompanies it (rate date, derivation method, attribution). This clearly separates it from generic siblings like fx_convert or fx_latest, though the quote direction (THB per USD vs USD per THB) is not stated, leaving the agent to infer it from the name.

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: 'Official ... reference rate' and 'no estimate' suggest this is for authoritative/reference use rather than ad-hoc conversion, which is useful signal. However, it never says when to prefer this over siblings such as fx_usd_thb (inverse pair), fx_convert, or fx_timeseries, and gives no exclusions or prerequisites beyond the price tag.

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