Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cad_omr

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the load and does reasonably well: it discloses the payment requirement and price ($0.002 USDC/call via x402 on eip155:8453), which an agent must know before calling. It also states the data is deterministic and sourced rather than estimated, and describes the returned components (rate date, method, source attribution). It does not cover failure modes or staleness handling, which keeps it below 5.

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?

One dense sentence that front-loads the payment tag and then the semantic content. Every clause contributes (pair, source, peg fallback, return fields, determinism), though the bracketed billing prefix competes with the purpose statement for primacy.

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 parameterless, single-value tool with no output schema, the description covers the important surface: source, method of derivation including the peg case, returned metadata, and the cost of calling. Only error/edge behavior and the numerical shape of the rate are left unstated.

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 has zero parameters and an empty schema, so there is nothing to disambiguate; the baseline is 4. The description correctly adds no fabricated parameter guidance.

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?

States a specific verb+resource: the official CAD/OMR reference rate, and even names the origin (latest ECB fixing, or the official peg when OMR is pegged). The pair and the nature of the value are unambiguous, so an agent can distinguish this from conversion or time-series siblings without reading a schema.

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

Usage Guidelines2/5

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

There is no explicit when-to-use/when-not guidance. It never says to prefer fx_convert for arbitrary amounts, fx_timeseries for history, or fx_latest for the general latest rate. Usage is only implied by the tool name and the phrase 'reference rate'.

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