Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aud_qar

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

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?

No annotations are supplied, so the description carries the full burden, and it discloses important behavior: paid access at $0.002 USDC per call via x402 on eip155:8453, deterministic sourcing, no estimates, and included rate date, method, and source attribution. It does not explicitly state read-only/no-side-effect behavior or the exact response shape, but the reference-rate framing makes the operation clear.

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?

The description is compact and front-loads the paid-access metadata before the core purpose. Every clause earns its place by covering cost, protocol, source, method, determinism, and attribution without waste.

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?

With no output schema and no parameters, the description still covers the key returned context: rate date, method, source attribution, and the deterministic non-estimate guarantee. It could more fully specify the exact numeric format or response envelope, but it is largely complete for a simple reference-rate 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?

The tool has zero input parameters, so there is no parameter meaning to clarify and the baseline is 4. The description appropriately avoids irrelevant parameter discussion.

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 clearly identifies the specific resource: the official AUD/QAR reference rate sourced from the latest ECB fixing or the official peg. This is clear and concrete, but it does not explicitly differentiate itself from closely related siblings such as fx_latest, fx_convert, or fx_timeseries beyond the pair-specific tool name.

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?

The description gives no explicit when-to-use guidance and does not name alternatives or exclusions. Usage is only implied by the currency pair and the mention of 'latest' fixing, so an agent must infer when this tool is preferable to fx_latest, fx_convert, or historical tools.

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