Skip to main content
Glama

Novarithm Agent Hub: trust and commerce checks

fx_eur_hkd

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses payment ($0.002 USDC/call via x402 on eip155:8453), data source (ECB), determinism, and the no-estimate guarantee. It does not cover failure modes, update cadence, or response format details beyond the listed fields.

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 that front-loads the payment tag and then the purpose, with every clause adding useful information. It avoids redundant restatement of the name and stays compact.

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 rate lookup with no output schema, the description explains the source, the method, and the key return fields (rate date, method, source attribution). That is sufficient for an agent to call it correctly without additional structured output documentation.

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 no parameter meaning to add beyond the schema. The baseline for 0 params is 4.

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?

The description names the exact currency pair and source (official EUR/HKD reference rate, latest ECB fixing) and explains the peg fallback. An agent can distinguish it from other fx_* pair tools by the pair encoded in the name and the stated source.

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?

It gives clear context for when the tool applies — retrieving the latest official ECB reference rate for EUR/HKD, including peg handling — but does not explicitly route the agent to or away from siblings like fx_latest or fx_convert. It also states no exclusions or preconditions beyond payment.

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.