Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aed_try

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

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 at all, the description carries the full burden and does substantial work: it discloses the $0.002 USDC cost, the x402 payment scheme, the chain (eip155:8453), the authoritative source, the peg fallback, and that the result is deterministic rather than estimated. It omits failure/staleness behavior (e.g., what is returned before the daily fixing publishes), which keeps it short of a 5.

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?

Two sentences, front-loaded with the payment term an agent must know before calling, then the precise resource definition. No filler; even the short closing phrase ('Deterministic, sourced, no estimate') adds a real quality guarantee.

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-argument, single-value lookup, the description covers source, derivation method, cost, and determinism. Because there is no output schema, the exact response field names and format are only sketched ('rate date, method, source attribution'), which is the one remaining gap.

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 the baseline is 4 and there is nothing for the description to disambiguate. The description instead describes what the response will contain (rate date, method, source attribution), which is a bonus at this level.

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 names a concrete resource with a specific pair ('Official AED/TRY reference rate'), the publishing authority (ECB fixing), and the derivation path. It never explicitly distinguishes itself from the other fx_* general tools in the sibling list (fx_latest, fx_timeseries, fx_convert), so an agent must infer that this is a single-pair spot lookup rather than a history or conversion 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 only implied: an agent can infer 'call this to get the latest AED/TRY rate,' and the peg caveat hints at edge-case behavior. There is no explicit when-to-use or when-not-to-use statement, and no routing to fx_timeseries for history or fx_convert for amount conversion.

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