Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cny_pln

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the paid x402 access cost ($0.002 USDC/call) and network (eip155:8453), states data provenance (ECB fixing, official peg), and explicitly says results are deterministic with no estimation. It does not cover freshness cadence beyond 'latest' or error/fallback behavior, which is a real but modest gap.

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?

A single dense sentence with the cost/access tag front-loaded, then the definition and its qualifiers. Everything stated earns its place; density is high but the reading order (cost, then what, then guarantees) is sensible.

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 tool with no output schema, the description anticipates the return contents (rate, rate date, derivation method, source attribution) and rules out estimation, which is what an agent needs to trust the call. Missing is any statement of refresh cadence or behavior when no fixing is available for the day.

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 no parameter meaning to add; baseline is 4. The description correctly implies the rate is fully determined by the tool's identity with no input required.

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?

States a specific verb-and-resource pair: 'Official CNY/PLN reference rate: latest European Central Bank fixing', plus peg fallback and derivation method. The pair is named in the title/name, but the description makes the source and semantics concrete. It does not explicitly differentiate from siblings like fx_convert or fx_latest, which keeps it below a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance and no named alternative, despite a huge family of sibling pairwise tools plus fx_convert, fx_latest and fx_timeseries that an agent must choose between. The purpose implies usage, but nothing steers selection for cross-rate, time-series, or conversion needs.

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