Skip to main content
Glama

Novarithm Agent Hub: trust and commerce checks

fx_omr_eur

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description still discloses paid access ($0.002 USDC/call via x402/eip155:8453), deterministic sourced data, ECB fixing, peg fallback, and included metadata. It stops short of rate limits, error behavior, or update cadence.

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?

A single dense sentence front-loads payment terms, then states purpose and return metadata; every clause is relevant. It could be marginally cleaner by separating cost from rate description, but there is no wasted text.

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-param lookup with no output schema, it names the returned components (rate date, method, source attribution) and the data-quality stance ('no estimate'). Only minor operational details such as update frequency or precision are missing.

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?

Zero parameters means there is nothing for the description to clarify; the baseline for a no-param tool is 4. Schema coverage is 100% and the schema is empty, so no additional parameter semantics are needed.

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?

States the exact pair and rate type: 'Official OMR/EUR reference rate: latest European Central Bank fixing', including the official-peg fallback. This is a specific resource and source, though it does not explicitly differentiate itself from sibling tools like fx_convert or fx_latest.

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?

The phrase 'reference rate' implies official/reference-rate usage, and the ECB/peg sourcing gives useful context. However, it never states when to choose this over fx_convert, fx_latest, or fx_timeseries, nor any when-not conditions.

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.