Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_nok_pln

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

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, the description carries the full burden and does well: it discloses the data source (ECB fixing), the methodology and peg fallback, the inclusion of rate date and attribution, the determinism guarantee ('no estimate'), and the billing model ($0.002 USDC via x402, eip155:8453). It omits staleness/caching behavior and numeric precision.

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 definition is a single dense sentence with a payment banner prefixed. All clauses (source, fallback, returned fields, determinism) earn their place; only the x402 tag is somewhat meta noise for invocation, but it is front-loaded and relevant to cost decisions.

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 covers most of what an agent needs: source, direction of the pair, returned metadata (rate date, method, attribution), and a determinism guarantee. Precision/scale of the numeric rate and currentness window are the only notable gaps.

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 schema semantics to supplement; the description's job is only to establish that the pair is fixed inside the tool, which the title and text do. Baseline 4 applies for a parameterless 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 and pair ('Official NOK/PLN reference rate: latest European Central Bank fixing') and explains the fallback case (official peg). It is unambiguous about what is returned, though it never names sibling tools such as fx_pln_nok (inverse pair) or fx_convert to make the boundary explicit.

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 by the stated source of truth ('official ECB fixing') and the price tag signals a paid call, so an agent can infer this is for authoritative reference rates rather than ad-hoc conversion. However, there is no explicit when-to-use versus fx_convert, fx_latest, fx_timeseries, or the reverse fx_pln_nok.

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