Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sar_omr

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

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 supplied, the description carries the burden and does well: it discloses the paid x402 call at $0.002 USDC on eip155:8453, the authoritative source (ECB fixing or official peg), and the method (direct, cross via EUR, peg-derived). It does not cover failure modes such as missing fixings on weekends/holidays or what the error response looks like.

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?

Two dense sentences, front-loaded with the price/payment tag and then the purpose. Every clause adds information: source, peg fallback, rate date, derivation method, and the deterministic/no-estimate guarantee.

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-parameter read tool with no output schema and no annotations, the description covers the essentials: cost/auth mechanism, data source, return fields, and the no-estimate guarantee. Minor gap is behavior when the ECB has no fixing for the day or what the response envelope looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema itself is trivially complete and there is no parameter meaning for the description to add. The description instead explains the return fields (rate date, method, attribution), which is useful but does not fall under parameter semantics.

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 a specific verb-like operation on a specific resource: 'Official SAR/OMR reference rate: latest European Central Bank fixing.' The pair and source are fixed, so it is instantly distinguishable from fx_latest, fx_convert, fx_timeseries and the hundreds of other single-pair fx_* siblings.

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?

Implicit guidance is present: 'latest ... fixing' signals a current spot lookup, which implicitly rules out historical series (fx_timeseries) or conversions (fx_convert). However, it never explicitly says when to prefer this over fx_latest or fx_sar_usd/fx_usd_omr, and there are no stated prerequisites or exclusions.

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