Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_ils_sek

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real value: the x402 payment model, price ($0.002 USDC/call on eip155:8453), data provenance (ECB fixing, peg fallback), and the deterministic/no-estimate guarantee. It stops short of describing failure behavior (what happens on a non-publishing day or a bank holiday), response shape, or rate precision, which matter for a paid call.

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 sentences with no filler, and the core purpose follows immediately after the billing prefix. The pricing prefix is arguably front-loaded above the actual purpose, but it is short enough not to obscure the function.

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-argument, no-output-schema tool, the description covers purpose, provenance, method disclosure, and the returned fields (rate date, method, source attribution). The one meaningful omission is quote direction and rounding convention for the ILS/SEK pair, which an agent cannot otherwise determine.

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, which is the baseline-4 case. The description reinforces this by stating it returns the 'latest' fixing, making clear there is no date, amount, or base-currency argument to supply.

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 resource ('Official ILS/SEK reference rate', 'latest European Central Bank fixing') and states the verb implicitly (retrieve the current fixing). The currency pair is unambiguous given the tool name. It does not, however, contrast itself with siblings such as fx_convert or fx_timeseries, so an agent must infer the boundary from the name alone.

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 rather than stated: the agent can infer this is the tool for a spot reference rate rather than a conversion or a historical series. There is no explicit 'use this when / use X instead' guidance, and no mention of what to do if a historical date is needed (fx_timeseries) or an amount must be converted (fx_convert).

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