Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xaf_myr

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

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, the description carries the full burden and does well: it discloses the paid model ($0.002 USDC/call, x402, eip155:8453), the peg fallback path when MYR is pegged, the derivation method, and that the result is deterministic and sourced rather than estimated. It omits failure behavior, such as what is returned when no ECB fixing is available for a date.

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 with the payment/x402 tag front-loaded and the substance (source, peg fallback, returned provenance fields) following immediately. It is efficient, though the parenthetical cost prefix and the trailing 'Deterministic, sourced, no estimate' slightly overlap in message.

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?

No output schema exists, and the description compensates by enumerating what comes back: the rate, the rate date, the derivation method, and source attribution. For a zero-parameter single-value lookup that is nearly complete; only error and staleness handling are unstated.

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 correctly implies the pair is fully determined by the tool name and that no amount or date argument is accepted, matching the empty schema.

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?

Names a specific verb and resource: the official XAF/MYR reference rate, latest ECB fixing. The currency pair is fixed in the name and restated in the description, so it is trivially distinguishable from the hundreds of fx_* siblings and from fx_convert, fx_latest, and fx_timeseries.

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?

Implicitly scopes usage to the latest published fixing by saying 'latest European Central Bank fixing', which rules out historical or time-series needs, but it never names alternatives such as fx_timeseries for history or fx_convert for amount conversion, and gives no when-not guidance.

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