Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aed_isk

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does well: it states the cost and payment mechanism ('PAID $0.002 USDC/call, x402, eip155:8453'), the data source (ECB), and the fallback behavior when ISK is pegged. It does not cover failure modes, staleness bounds beyond 'latest', or what happens if the fixing is unavailable.

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?

Effectively two sentences: a bracketed pricing/payment prefix followed by a single front-loaded sentence covering source, value, and returned metadata. Dense but every clause adds information; nothing is filler.

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, no-output-schema tool with no annotations, the description supplies the essentials an agent needs: source authority, determinism guarantee, cost, payment protocol, and the metadata returned alongside the rate. Coverage of error and freshness edge cases is the only notable gap.

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 in the schema for the description to clarify; baseline 4 applies. The description instead spends its words on output semantics (rate date, method, attribution), which is appropriate for a no-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 resource (AED/ISK) and a specific source and verb ('Official AED/ISK reference rate: latest European Central Bank fixing'), which is unambiguous. It does not explicitly contrast itself with siblings such as fx_convert or fx_latest, but the pair-specific name plus the 'reference rate' framing make the boundary reasonably obvious.

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 only implied: an agent can infer this is the tool to call for a sourced AED/ISK spot reference and not for estimates ('Deterministic, sourced, no estimate'). However, there is no explicit when-to-use statement, no mention of alternatives like fx_convert or fx_timeseries, and no note on what to do when ISK is pegged versus free-floating.

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