Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sek_chf

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

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 full burden and does well: it discloses the paid x402 access model ($0.002 USDC/call, eip155:8453), the data provenance (ECB fixing, peg-derived when applicable), and that results are deterministic with no estimation. It does not say what happens when no fixing exists (weekends/holidays) or how stale the cached rate can 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?

A single dense sentence with no filler, and the payment/access terms are front-loaded before the data claim. The bracketed x402 tag is slightly noisy for an agent that only wants the rate, but it is operationally necessary information rather than padding.

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 what is returned (rate, rate date, method, source attribution), the cost and payment rail, and the determinism guarantee. The remaining gap is operational: no update cadence or no-data behavior, which matters for a rate that only publishes on ECB business days.

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 and the baseline of 4 applies. The description correctly focuses its words on provenance rather than non-existent inputs.

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 and scope: 'Official SEK/CHF reference rate: latest European Central Bank fixing'. The verb/resource pairing plus the peg caveat lets an agent distinguish this from the hundreds of other fx_<pair> siblings and from fx_convert/fx_latest without opening any 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 pair-specific name and by 'reference rate' phrasing, and the peg fallback is disclosed. However, there is no explicit routing guidance versus fx_convert (conversion) or fx_latest (multi-pair snapshot), and no stated preconditions beyond the payment tag.

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