Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xaf_thb

[PAID $0.002 USDC/call, x402, eip155:8453] Official XAF/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_xaf_thb"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With zero annotations the description carries the full burden, and it delivers unusually valuable operational facts: a paid endpoint at $0.002 USDC/call over x402 on eip155:8453, plus the returned metadata (rate date, derivation method, source attribution) and a determinism/staleness guarantee ('Deterministic, sourced, no estimate'). It still omits what payment handshake is required to actually execute and what happens on non-fixing days or failed peg derivation.

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?

One dense sentence plus a bracketed price/protocol tag, with no filler. The cost tag leads rather than the purpose, which is mildly suboptimal for a selection decision, but the remainder is front-loaded with the currency pair and source.

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 the returned fields (rate date, method, source attribution) and asserting the rate is deterministic and non-estimated. Combined with the x402 payment disclosure, an agent has nearly everything needed; only the payment-execution mechanics and stale/failure behavior are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the baseline is 4, but the description spends its budget elsewhere and adds nothing about invocation semantics beyond the fixed pair. Nothing is misdocumented; there is simply nothing parameter-level to add.

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 the exact pair (XAF/THB), the exact source (latest European Central Bank fixing), and the value semantics including the peg fallback ('or the official peg when THB is pegged'). This is unambiguous against the sibling wall of fx_* pair tools, since the direction and source are both pinned down in the first clause.

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?

Implicit only: naming it a 'reference rate' and 'latest fixing' signals a point-in-time official rate rather than conversion (fx_convert) or history (fx_timeseries), but no alternative is named and no when-to-use or when-not-to-use condition is stated. An agent must infer routing from the name and from the 'no estimate' qualifier.

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