Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_kmf_eur

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 behavioral burden and does substantial work: it discloses the paid x402 model ($0.002 USDC/call on eip155:8453), the data source (ECB fixing), peg fallback behavior, and that the value is deterministic with no estimation. It stops short of covering freshness/lag, failure modes, or what happens when EUR is pegged to a non-KMF currency.

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?

One front-loaded sentence with the price tag bracketed up front, followed by source, method and return fields — no filler. Slightly dense with parentheticals, but every clause (peg handling, method, attribution) carries information an agent needs.

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?

There is no output schema, and the description compensates by naming the return fields (rate, rate date, method, source attribution) and the method variants. Given the tool's low complexity (no inputs, single scalar result), this is nearly complete; only staleness expectations and error behavior are absent.

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 add; the baseline for a 0-param tool applies. The description correctly implies the currency pair is baked into the endpoint, so no argument selection is required.

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?

States a specific resource (KMF/EUR reference rate) and its provenance (latest ECB fixing, or the official peg when EUR is pegged). An agent can immediately tell it returns a single spot rate rather than a conversion (fx_convert) or a series (fx_timeseries), though the inverse-direction sibling fx_eur_kmf is not explicitly disambiguated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use / when-not-to-use guidance and no routing to alternatives. Among hundreds of fx_* siblings, an agent gets no help deciding between this, fx_eur_kmf (inverse), fx_convert (arbitrary amount conversion) or fx_timeseries (historical), so the choice must be inferred from the name alone.

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