Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sek_mxn

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 model ($0.002 USDC/call on eip155:8453), the authoritative source (ECB), the derivation method (direct, cross via EUR, or peg-derived), and that values are deterministic/non-estimated. Gaps remain around freshness/staleness limits, error behavior when a fixing is unavailable, and whether the response is a single scalar or an object.

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 the payment/transport metadata bracketed up front and the substantive content front-loaded after it. The parenthetical 'direct, cross via EUR or peg-derived' earns its place by explaining rate derivation. Dense but no filler.

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?

For a zero-parameter, no-output-schema lookup tool, the description supplies source, method, exactness guarantee, and cost. An agent can decide to call it and know what it will get without further schema inspection.

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 schema to document and nothing for the description to disambiguate. The description correctly implies that the currency pair is fixed by the tool identity rather than supplied as input.

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 concrete resource and producer: 'Official SEK/MXN reference rate: latest European Central Bank fixing (or the official peg when MXN is pegged).' That is far more than the name alone conveys. It does not explicitly route to siblings (e.g. fx_convert for conversion, fx_timeseries for history), relying instead on the pair-naming convention shared by hundreds of fx_* tools.

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: it is clearly the tool for a single spot reference rate, and 'no estimate' hints at when precision matters. But there is no explicit when-to-use/when-not guidance, no mention of fx_convert for actual conversion or fx_timeseries for historical series, and no note about the payer/payment flow required before calling.

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