Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_thb_cny

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

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 does substantial work by disclosing the exact $0.002 USDC per-call charge, x402 payment requirement, eip155:8453 network, determinism, provenance, calculation-method reporting, and absence of estimation. It is less explicit about read-only behavior, ECB publication delays or staleness, and payment or source-failure handling.

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 definition is compact and front-loads the cost before giving a dense but readable account of purpose, source, returned context, and reliability. The bracketed payment tag and two sentences contain no substantial filler.

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-argument lookup without an output schema, it covers the source, rate date, calculation method, attribution, determinism, and payment requirements, making selection and invocation straightforward. It would be more complete if it stated the quote direction explicitly, such as CNY per one THB, and clarified fixing availability or routed conversion and historical requests to appropriate siblings.

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 parameters, so no argument semantics require explanation. The fixed pair and "latest" wording also make the no-input invocation clear.

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?

"Official THB/CNY reference rate" and "latest European Central Bank fixing" precisely identify the resource, currency pair, and latest-reference semantics, while the rate date, method, and attribution clarify what accompanies the rate. It does not explicitly distinguish this lookup 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 description supplies a clear use case: select it for the latest official, sourced THB/CNY reference rate rather than an estimated value. It provides no explicit when-not guidance or alternatives for amount conversion, other currency pairs, or historical series.

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