Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sek_xaf

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full burden and does most of it: it discloses the paid x402/USDC cost and chain (eip155:8453), the determinism guarantee, the 'no estimate' policy, and that source attribution and rate date accompany the value. Gaps remain on the payment flow prerequisites and on behavior when no fixing exists (weekends/holidays).

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 plus a bracketed payment tag, front-loaded with cost then purpose, with no filler. The phrase 'the method (direct, cross via EUR or peg-derived)' is slightly heavy but earns its place by telling the agent how to interpret the returned rate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description names the returned components (rate date, method, source attribution) and the fallback logic (peg when XAF is pegged), which is exactly the return-value information the agent would otherwise lack. For a zero-parameter, single-value lookup, nothing material is missing.

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 there is nothing for the description to disambiguate; baseline 4 applies. It correctly makes no parameter claims that could conflict with the empty schema.

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 precise resource (SEK/XAF reference rate) and its exact provenance (ECB fixing, or the official peg when XAF is pegged), plus the method axis (direct, cross via EUR, peg-derived). Against a family of hundreds of near-identical fx_<AAA>_<BBB> siblings, this makes the pair and the data source 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 by the pair name and the 'reference rate' framing, but there is no explicit when-to-use versus fx_convert, fx_latest or fx_timeseries, and no statement of when not to use it (e.g. for historical series or for conversion arithmetic).

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