Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aed_omr

[PAID $0.002 USDC/call, x402, eip155:8453] Official AED/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_aed_omr"
  }
}

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 carries the full burden and does a lot: it discloses the paid cost and payment scheme (x402, $0.002 USDC on eip155:8453), the authoritative source (ECB fixing), the peg fallback path, and that output includes rate date, derivation method and source attribution. It explicitly rules out estimation ('deterministic, sourced, no estimate'). Gaps: no statement of refresh cadence/staleness (ECB publishes on business days only) or error behavior for non-publication days.

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?

Two sentences, front-loaded with the cost tag then the resource, and no filler. The second sentence is dense with parentheticals ('direct, cross via EUR or peg-derived') but every clause carries operational meaning, so the only cost is a slightly run-on reading.

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?

There is no output schema, and the description compensates by naming the returned fields (rate date, method, source attribution) plus the quote semantics implied by 'AED/OMR reference rate'. Missing pieces are the numeric precision/rounding and the publication cadence, which matter for a rate tool but are secondary for a zero-parameter lookup.

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 input parameters, so the baseline is 4; there is nothing in the schema for the description to elaborate. The pair is fixed in the tool name, which is consistent with the empty object schema.

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 resource and scope: the AED/OMR reference rate from the ECB fixing, with a named fallback (official peg when OMR is pegged). The currency pair in the name plus the 'reference rate' framing separates it from the sibling conversion tool (fx_convert) and from history/latest siblings without the agent needing to open any schema.

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 pair-specific naming and by 'reference rate', but there is no explicit when-to-use / when-not guidance and no routing to alternatives such as fx_convert (amount conversion), fx_latest (all pairs), or fx_timeseries (history). The agent must infer that this returns a single rate rather than performing a conversion.

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