Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_krw_pln

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 mostly succeeds: it discloses the payment model and amount ($0.002 USDC/call, x402, eip155:8453), the authoritative source (ECB fixing), the derivation method (direct, cross via EUR, peg-derived), and a determinism guarantee ('no estimate'). Gaps remain around freshness cadence, error behavior, and what happens when no fixing exists for a date.

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?

A single dense sentence plus a bracketed cost prefix — no filler. The cost/x402 metadata is front-loaded where a paying agent needs it, then purpose, source, method, and guarantees follow in a logical order.

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, single-value lookup with no output schema, the description covers source, method, returned fields (rate date, method, attribution), and cost — enough to call it correctly. Missing only operational details like publication timing and the failure mode when no fixing is available.

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 semantics to explain; baseline of 4 applies. The description correctly signals a no-input, single-pair call by specifying the currency pair in prose rather than requiring arguments.

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 states a specific resource — 'Official KRW/PLN reference rate' — and pins it to the ECB fixing, which is far more informative than the name alone. It does not explicitly differentiate itself from nearby siblings such as fx_convert (arbitrary conversion) or fx_timeseries (history), though 'latest fixing' implicitly excludes the historical tool.

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 pair-specific naming and the word 'latest', so an agent can infer 'call this when you need the current KRW→PLN rate'. However, there is no explicit when-to-use/when-not guidance and no named alternative for conversion of amounts or for historical series, which matters given hundreds of sibling fx tools.

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