Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_chf_krw

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 payment model ($0.002 USDC per call, x402, eip155:8453), the authoritative source (ECB fixing), the fallback behavior when KRW is pegged, and that the result is deterministic and never estimated. It stops short of stating publication cadence/freshness (ECB fixes on business days only) or what a caller should expect on weekends and holidays.

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?

Two sentences/fragments with essentially no waste — payment terms, data source, method, and determinism guarantee all earn their place. The price bracket leads, which is defensible as gating information but does push the actual purpose to second position.

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?

With no output schema, the description correctly enumerates what comes back: the rate, the rate date, the derivation method (direct, cross via EUR, or peg-derived), and source attribution. That is close to complete for a zero-parameter lookup; only freshness rules for non-publication days are missing.

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 nothing for the description to disambiguate. The baseline of 4 applies; no parameter semantics gap exists.

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?

States a precise resource: the official CHF/KRW reference rate, specifically the latest ECB fixing (or the official peg when KRW is pegged). This is unambiguous against the huge sibling set of fx_<base>_<quote> pairs, since the pair is named and the data source is pinned to the ECB.

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 name and description — call it to get the current CHF/KRW reference rate. There is no explicit routing guidance such as using fx_convert for arithmetic conversions or fx_timeseries for historical series, nor any statement about when this tool should not be used. The per-call price is stated, which implicitly signals a cost consideration but is not framed as guidance.

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