Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_krw_eur

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

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 it delivers real context: a paid x402 endpoint at $0.002 USDC/call on eip155:8453, ECB as the source, peg-vs-direct-vs-cross method disclosure, and a 'deterministic, no estimate' guarantee. Gaps remain on weekend/holiday and intra-day staleness behavior and on the exact shape of the returned record.

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 plus a bracketed cost tag, with no filler — every clause (source, method, attribution, determinism) adds information. The structure is slightly off-front-loaded, since the paid/billing metadata precedes the actual purpose, but nothing is wasted.

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 rate lookup with no output schema and no annotations, the description covers what matters: source, method, rate date availability, determinism and cost. It stops short of stating quoting convention (KRW per EUR), rate precision, or update cadence, which would complete the picture for a fixings tool.

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 for a parameterless tool applies. No misleading parameter talk is present.

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 specific verb+resource: 'Official KRW/EUR reference rate' from the 'latest European Central Bank fixing', including the peg fallback. The currency pair is encoded in the name and restated with its authoritative source, so the agent can distinguish it from siblings like fx_convert, fx_latest or fx_timeseries without opening a schema.

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?

Usefulness is implied by the pair name and the phrase 'reference rate', so an agent needing a KRW-per-EUR fixing can infer the call. However, the description never states when to prefer this over fx_convert (conversion), fx_latest (multi-pair snapshot) or fx_timeseries (history), and gives no exclusions or freshness caveats.

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