Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sek_zar

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden and does useful work: it discloses the payment model and price ($0.002 USDC/call via x402 on eip155:8453), the data method (direct, cross via EUR, or peg-derived), and that the output is deterministic with source attribution rather than an estimate. It omits operationally important behavior: fixing publication cadence, what happens on weekends/holidays or when no fixing exists, and error behavior.

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?

One dense, front-loaded block: price tag first, then what the rate is, then fallback method, then attribution and determinism claim. Every clause is informative; the only mild redundancy is 'Deterministic, sourced, no estimate' restating the attribution clause.

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, annotation-free, no-output-schema tool, the description covers source, methodology, edge case (peg), and returned components (rate, date, method, attribution). Remaining gap is response shape and stale/absent-fixing behavior, but it is broadly sufficient to call the tool correctly.

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 the baseline is 4. The description correctly requires no argument explanation and instead spends its text on output semantics and sourcing.

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?

Names a specific resource (the SEK/ZAR official reference rate) and a specific source (latest ECB fixing), plus the peg fallback. Against a sibling list of hundreds of fx_<base>_<quote> tools, the pair is stated explicitly in both name and description, so the agent can select it without opening the 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 rather than stated: 'latest ... fixing' signals this is for a current official rate, which implicitly rules out historical series (fx_timeseries) and conversions (fx_convert). However, no alternative sibling is named and no when-not condition is given, so the agent must infer the boundary.

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