Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_pln_chf

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 load and does well: it discloses the payment model and price ($0.002 USDC/call, x402, eip155:8453), the data provenance (ECB fixing, or official peg), the derivation method (direct, cross via EUR, peg-derived), and that the rate is deterministic rather than estimated. It stops short of stating behavior for non-publication days or what happens on upstream failure, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence that front-loads the cost and network, then the resource, source, and fallback semantics. Every clause adds information an agent would otherwise have to guess, and nothing is repeated from structured fields.

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 read tool with no output schema, the description usefully previews the returned fields (rate date, method, source attribution). The one ambiguity left is quote direction, since 'PLN/CHF' does not state whether the rate is PLN-per-CHF or CHF-per-PLN.

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 and there is no schema surface the description needs to compensate for. The pair is baked into the tool name, which the description confirms.

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?

The description names a specific resource (official PLN/CHF reference rate) with a specific source (European Central Bank fixing) and explicitly covers the peg fallback. An agent can distinguish this from fx_convert or fx_latest because the currency pair and the authoritative-source claim are both stated up front.

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 by the pair name: an agent infers this is the tool for PLN-to-CHF lookups rather than a conversion or a time series. There is no explicit statement of when to prefer it over siblings such as fx_convert or fx_timeseries, and no exclusions or prerequisites beyond the paywall note.

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