Skip to main content
Glama

Novarithm Agent Hub: trust and commerce checks

fx_xof_thb

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description discloses the per-call price, USDC currency, x402 payment mechanism, and eip155:8453 network. It also explains determinism, sourcing, the absence of estimation, and the possible direct, EUR-cross, or peg-derived calculation methods.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The payment requirement is front-loaded, followed by the purpose, methodology, and returned context in two compact sentences. The wording is dense but contains little unnecessary material.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-input rate lookup, the definition supplies the information needed to invoke it confidently: cost, payment rails, pair, recency, authoritative basis, determinism, and expected rate metadata. Although there is no output schema, the description adequately identifies the principal returned values.

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?

There are no input parameters, so the baseline score applies. The description usefully confirms that the currency pair and latest-rate scope are fixed rather than caller-supplied.

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 clearly identifies the fixed XOF/THB pair, the latest official reference rate, and the ECB fixing or peg-derived basis. It also lists the rate date, calculation method, and source attribution, but does not explicitly differentiate the tool from siblings such as fx_convert, fx_latest, or fx_timeseries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The wording establishes a clear use case: obtaining a current, official, sourced XOF/THB reference rate rather than an estimate. It does not explicitly say when not to use it or route conversion and historical-rate requests to the relevant sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.