Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_aed_inr

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden and delivers real behavioral context: a paid call ($0.002 USDC, x402, eip155:8453), the underlying source (ECB fixing vs official peg), and a determinism/no-estimate guarantee. It does not cover failure or staleness behavior (e.g., weekends/holidays when no ECB fixing publishes), which is the main 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?

Two sentences, front-loaded with the cost/transport tag then the substance, with no filler. The bracketed payment prefix is dense but sits out of the way, and every clause (source, method, date, determinism) adds information.

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, no-annotation tool the description covers the essentials an agent needs: what the rate is, where it comes from, how it was derived, and that it is authoritative rather than estimated. Only the return shape and no-data/staleness behavior are left unstated, which is a modest but real gap given no output schema exists.

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; this sits at the baseline of 4. The response fields it does allude to (rate date, method, source attribution) are useful framing but not parameter semantics.

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 and scope: 'Official AED/INR reference rate' plus the concrete upstream ('latest European Central Bank fixing'). The currency pair in the name plus this sentence lets an agent tell it apart from the hundreds of other fx_* pair tools. It stops short of naming which sibling to use for conversion or history, so it does not fully distinguish its role in the family.

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: the pair name makes the obvious case clear, and 'no estimate' hints it's the authoritative fix. There is no explicit guidance such as 'use fx_convert for arithmetic' or 'use fx_timeseries for historical series', nor any note about what to do when a call fails or when a non-ECB pair is needed.

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