Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_gbp_inr

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 does substantial work: it discloses a paid endpoint ($0.002 USDC/call, x402, eip155:8453), the authoritative data source (ECB), a fallback behavior (official peg when INR is pegged), the fact that the method is disclosed in the response, and that values are deterministic with no estimation. Remaining gaps are rate limits and any staleness/fixing-cadence behavior.

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 (one dense sentence plus a short qualifier), front-loaded with the cost/payment prefix and then the core resource. Every clause carries information — source, date, method, attribution, determinism — though the single long sentence could be split for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with no output schema, the description compensates by describing the returned fields (rate, rate date, method including cross-via-EUR or peg-derived, source attribution) and the payment mechanics. An agent has everything needed to decide to call it and interpret the result.

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. The description adds no parameter meaning, which is appropriate here since there is nothing to parameterize — the pair is fixed by the tool name.

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 GBP/INR reference rate' with 'latest European Central Bank fixing'. The pair GBP/INR is explicit in the name and description, so an agent can distinguish it from the hundreds of sibling fx_* pair tools and from fx_convert/fx_latest/fx_timeseries without opening any schema.

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

Usage Guidelines4/5

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

Gives a clear context for use: the latest ECB fixing, deterministic and sourced, 'no estimate' — which implicitly steers away from estimate-based tools. It does not explicitly name alternatives (e.g., fx_convert for arbitrary conversions, fx_timeseries for history), so the when-not guidance is inferred rather than stated.

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