Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_usd_aed

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

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 carries the full burden and does substantial work: it discloses the cost ($0.002 USDC/call), the payment protocol (x402, eip155:8453), the authoritative source (ECB fixing), the fallback to official peg, and the derivation method (direct, cross via EUR, peg-derived). It also guarantees determinism and no estimation. Gaps remain around non-fixing days, staleness, and error behavior, which matters for a rate tool.

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 plus a bracketed pricing/protocol prefix. The payment and source facts are front-loaded and every clause carries information. It is slightly packed, but virtually no filler is present.

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?

No output schema exists, and the description compensates by naming the returned fields: the rate itself, the rate date, the derivation method, and source attribution. For a zero-parameter, single-value tool this is close to complete; only payment-flow mechanics and holiday/weekend behavior are unaddressed.

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 takes zero parameters, so the baseline is 4. The description usefully reframes the implicit inputs as fixed by the tool name and spends its words on what the single call returns instead.

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?

The description gives a specific verb-and-resource pairing: it returns the USD/AED reference rate, names the data source (ECB fixing), and states the peg fallback behavior. Direction is consistent with the tool name (USD base, AED quote). It does not explicitly distinguish itself from the inverse sibling fx_aed_usd or from fx_latest, but the pair-specific naming makes the target unambiguous.

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 rather than stated: an agent can infer this is the tool for a single spot USD/AED rate. There is no explicit when-to-use or when-not, no mention of fx_latest, fx_timeseries, fx_convert, or the inverse fx_aed_usd pair as alternatives. 'Deterministic, sourced, no estimate' is a quality claim, not routing guidance.

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