Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cad_qar

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

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 whole burden and does well: it discloses the price ($0.002 USDC/call), the payment protocol (x402) and network (eip155:8453), the data provenance (ECB fixing, peg fallback), and the computation method (direct, cross via EUR, peg-derived). It only omits what happens on non-fixing days and how stale the rate may be.

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 compact segments with no filler, and the rate definition is stated up front after the payment tag. The bracketed cost/protocol prefix is arguably better placed after the purpose, but it is genuinely load-bearing information for a paid endpoint.

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?

Because there is no output schema, the description must imply the return shape, and it does — rate, rate date, method, and source attribution are all enumerated. What is missing is the numeric precision/quoting convention and behavior on weekends and holidays, which matter for a 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 takes zero parameters, so the baseline is 4; the description correctly requires no parameter explanation and instead spends its words on provenance and output content.

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 the exact resource and direction ('Official CAD/QAR reference rate') with a specific source (European Central Bank fixing) and fallback behavior (official peg when QAR is pegged). An agent can distinguish this pair tool from the hundreds of other fx_ pairs purely from the pair encoded in the name plus this confirmation of direction and source.

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?

Useful implied context exists — 'reference rate' and 'no estimate' signal this is for official/accounting-grade rates rather than tradeable market quotes — but the description never names alternatives such as fx_convert, fx_latest, or the inverse fx_qar_cad, nor states when to prefer them.

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