Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_qar_eur

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/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 so well: it discloses that the call is paid ($0.002 USDC), the payment protocol and chain (x402, eip155:8453), that the value is deterministic and sourced rather than estimated, and what methodology variants (direct, cross via EUR, peg-derived) may apply. Cost and payment mechanism are exactly the behavioral facts an agent must know before invoking a metered endpoint.

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?

A single dense sentence with no filler, and every clause (price, protocol, source, method, determinism) adds information. Minor deduction because the bracketed payment/chain preamble is front-loaded ahead of the actual purpose, delaying the part most agents need first.

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 lookup with no output schema, the description covers the essentials: source authority, rate date, method, and attribution fields the caller will receive. It stops short of stating the base/quote convention and how stale the "latest" fixing can be, which are the remaining facts an agent would want before relying on the number.

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 and there is nothing for the description to disambiguate. The one semantic gap is the quoting direction of "QAR/EUR," which the description does not pin down.

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?

States a specific resource ("Official QAR/EUR reference rate") and a specific source/verb ("latest European Central Bank fixing"), plus the fallback case ("official peg when EUR is pegged"). Against ~900 sibling pair tools this identifies exactly which currency pair and which pricing basis, so an agent can select it without opening the schema.

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 by the resource — an agent needing a QAR/EUR reference rate knows to call this — but there is no explicit when-to-use versus the generic siblings (fx_latest, fx_convert) or when to prefer a live/market rate over an ECB fixing. The peg fallback case is described, which helps, but no exclusions or alternative routing are given.

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