Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_jpy_sek

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

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?

No annotations exist, so the description carries the full burden and does well: it discloses the paid x402 flow ($0.002 USDC/call on eip155:8453), the data provenance (ECB), the peg fallback path, and that the result includes rate date, derivation method, and source attribution, plus a determinism/no-estimate guarantee. Gaps remain on publication cadence (how stale 'latest' can be) and failure behaviour, which matter for a rate lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no waste. The cost/payment tag is front-loaded so an agent sees the spend before the semantics, and the purpose, provenance, fallback, and return shape follow in a single readable sentence.

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 no-parameter, no-output-schema single-pair lookup, the description is nearly sufficient: it says what is returned (rate, date, method, attribution) and how it is derived. The only meaningful omission is freshness semantics, i.e. how often the ECB fixing updates and what 'latest' guarantees.

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, and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline of 4 applies for the parameter-free case.

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 states a specific resource (the official JPY/SEK reference rate) and a specific source (the latest ECB fixing), including the peg fallback. It is clearly distinct from neighbouring pair tools by naming the pair, but it never contrasts itself with the utility siblings fx_convert, fx_latest, or fx_timeseries, which sit alongside it in the same family.

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: 'latest ECB fixing' and 'no estimate' signal a single-pair official-snapshot lookup, but there is no explicit when-to-use, no when-not-to-use, and no routing to fx_convert for conversions or fx_timeseries for history. An agent must infer the choice from the name alone.

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