Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_eur_try

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

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 present, the description carries the full burden and does well: it discloses the x402 payment requirement and price ($0.002 USDC/call, eip155:8453), the data source (ECB fixing), the derivation method (direct, cross via EUR, or peg-derived), and the determinism guarantee. It stops short of stating cache/freshness windows or behavior on non-published days, which is the only 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.

Conciseness4/5

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

A single dense sentence plus a bracketed monetization tag, front-loaded and free of filler. The payment prefix is placed first and is genuinely decision-relevant, though it competes slightly with the purpose statement for first-token salience.

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, no-output-schema price lookup, the description covers source, method, fallback path, and payment terms — enough to call it correctly and interpret the result. The only missing piece is guidance on sibling alternatives (fx_convert / fx_timeseries) for time-series or conversion needs.

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 no parameters, so there is nothing for the description to disambiguate and the baseline applies. The description instead uses the space to define the fixed inputs implicitly (base EUR, quote TRY, source ECB).

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 and resource ('Official EUR/TRY reference rate: latest European Central Bank fixing') with the exact currency pair, which distinguishes it cleanly from the hundreds of sibling fx_* pair tools. It also names the fallback semantics (official peg) so the agent knows what value is returned.

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?

The description makes the usage context inferable ('reference rate', 'latest fixing', 'no estimate'), which signals a sourced official rate rather than a live market quote. However, it never names alternatives such as fx_convert, fx_latest, or fx_timeseries, nor says when to prefer this pair-specific tool over those.

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