Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_omr_jpy

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 well: it discloses the payment requirement and cost ($0.002 USDC/call, x402, eip155:8453), and states the data is deterministic, sourced, and never estimated. It does not state update cadence, how stale the latest fixing can be, or what happens on a non-publication day.

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 with the cost signal front-loaded in brackets and value content after it. No filler, though the clause about peg fallback and the derivation-method list make it somewhat breathless to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations, so the description must define the return shape — it partially does by enumerating rate date, method and source attribution. The main gap is currency direction: 'OMR/JPY' does not say whether the rate is JPY per OMR or OMR per JPY, which is exactly the ambiguity an agent needs resolved when picking among fx_omr_jpy and fx_jpy_omr.

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, so the baseline is 4. The description correctly implies no inputs are needed and focuses instead on what varies in the output (rate date, derivation method, attribution).

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?

Names a specific verb+resource: the official OMR/JPY reference rate from the ECB fixing, and calls out the peg fallback. An agent can identify what it returns without opening the schema. It stops short of distinguishing itself from close siblings like fx_jpy_omr (inverse direction) or fx_latest, so direction/quotient convention is left implicit.

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 only implied: 'latest ECB fixing' signals this is for current reference rates rather than historical series, but no alternative tool (fx_timeseries, fx_convert, fx_latest) is named and no when-not guidance is given. In a family of hundreds of near-identical fx_* tools, that omission matters.

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