Skip to main content
Glama

Novarithm Agent Hub: trust and commerce checks

fx_thb_nok

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose important traits: paid access, x402 protocol, source attribution, direct/cross/peg-derived method, and deterministic sourced data with no estimate. It does not cover rate limits, failure modes, or freshness guarantees beyond "latest."

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 description is a single dense sentence, with payment metadata followed by the resource, source, output attributes, and quality claim. It is front-loaded and contains no clearly wasted wording.

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-parameter data lookup with no output schema and no annotations, the description is complete enough to invoke correctly. It identifies the pair, source, method, and returned fields such as rate date and attribution.

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 zero parameters and the schema is empty, so there is little parameter meaning to add. The description sensibly focuses on the returned data attributes rather than inventing parameter semantics.

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 states a specific resource, the official THB/NOK reference rate, and a specific source, the latest ECB fixing or official peg. It does not explicitly contrast itself with generic siblings such as fx_latest or fx_convert, so it is clear but not fully differentiated.

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 by the phrase "latest ... reference rate" and "no estimate," suggesting this is for an official current-rate lookup. However, there is no explicit when-to-use or when-not guidance, and no named alternative for conversion or time-series needs.

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.