Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sek_qar

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

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 supplied, the description carries the full behavioral burden and does well: it discloses the paid x402 requirement ($0.002 USDC per call on eip155:8453), the authoritative source (ECB), and the derivation method (direct, cross via EUR, or peg-derived). It also asserts determinism and 'no estimate', which sets expectations about output stability. It stops short of describing failure behavior when a fixing is unavailable.

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?

The payment terms are front-loaded in a bracketed prefix, followed by a single dense sentence covering source, fallback, method and attribution. Nothing is redundant, though the sentence is long and could be split for faster scanning.

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, no-output-schema tool, the description covers what an agent most needs: cost and payment protocol, data provenance, rate date, derivation method and source attribution. The main residual gap is the absence of any guidance on alternatives among the many sibling fx_* tools.

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 description instead characterizes the implicit inputs, namely that the pair is fixed by the tool identity and that the fallback path is peg-derived when QAR is pegged.

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 names a specific verb and resource: 'Official SEK/QAR reference rate: latest European Central Bank fixing (or the official peg when QAR is pegged)'. The currency pair is unambiguous and matches the tool name. It does not, however, distinguish itself from siblings like fx_latest, fx_convert or fx_timeseries, so an agent must infer that this is the single-pair spot lookup.

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 by the pair encoded in the name and by the mention of the ECB fixing. There is no explicit when-to-use statement, no mention that fx_convert should be used for arbitrary amount conversion, and no note on when fx_latest or fx_timeseries would be preferable.

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