Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sgd_sek

[PAID $0.002 USDC/call, x402, eip155:8453] Official SGD/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_sgd_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 the description does disclose a great deal: cost ($0.002 USDC/call), payment protocol (x402, eip155:8453), deterministic sourcing, direct/cross-via-EUR/peg-derivation methods, and the fact that values are never estimated. However, it omits the refresh cadence (ECB publishes once per business day), stale-weekend behavior, and what happens when the pair is unavailable. For a paid endpoint, the cost disclosure is the most valuable part and it is present.

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?

It is a single dense sentence followed by a short list of returned attributes, with the payment terms front-loaded in a bracketed tag so they are easy to skip. Every clause earns its place, though the payment tag competes with the purpose statement for first position.

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?

There is no output schema, so the description must state the return shape, and it does: rate value, rate date, derivation method, and source attribution. For a zero-parameter lookup that is nearly complete; only freshness and error behavior are left unstated.

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?

There are zero parameters, so this dimension starts at the baseline of 4. The description correctly describes no inputs and instead describes implicit scope (one fixed pair, one fixed source), which is the right focus for a zero-arg tool.

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 verb and resource ("Official SGD/SEK reference rate") and its source ("latest European Central Bank fixing"), so an agent knows exactly what value it gets. It is clear without opening any schema, though it never distinguishes itself from the many sibling pair tools or from fx_latest/fx_convert, which the name alone must convey.

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?

Use is implied ("latest ... fixing", "no estimate") rather than stated: nothing says when to pick this over fx_latest, fx_convert, or fx_timeseries. There are no exclusions or precondition notes. Adequate for a zero-argument rate lookup, but the routing guidance is left to inference.

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