Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cny_isk

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description still discloses the $0.002 USDC per-call charge, x402 payment mechanism, and eip155:8453 network, along with the source-selection and conditional peg fallback. It also promises the rate date, method, and attribution and states deterministic, no-estimate behavior, providing unusually useful operational context for a simple lookup.

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?

The payment terms are front-loaded and the remaining text compactly covers source, methodology, returned metadata, and determinism. The main sentence is dense, and 'Deterministic, sourced, no estimate' partly repeats the official-source and attribution claims, so the wording is not perfectly economical.

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-argument lookup with no output schema, the description covers the key returned fields, provenance, derivation, and payment requirement. It still leaves the quote convention or units, publication and freshness behavior, and selection boundaries with generic FX siblings 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 no parameters, so the baseline is 4 and no argument documentation is needed. 'Latest' and the fixed pair also make clear that the caller does not supply a date, amount, or currencies.

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 identifies a fixed CNY/ISK latest reference rate, its ECB source, and possible derivation methods, so the resource and operation are clear despite the noun-phrase wording. The pair distinguishes it from other fixed-pair tools, but it does not explain how it differs from generic siblings such as fx_latest or fx_convert.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The terms 'latest,' 'official,' and 'no estimate' establish a clear use case: obtaining a current sourced reference rate rather than an estimated value. There is no explicit when-not guidance or routing to alternatives for historical series, amount conversion, or the inverse pair.

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