Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_myr_jpy

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description still carries strong behavioural detail: it declares the tool is paid ($0.002 USDC/call, x402, eip155:8453), that the value is deterministic and sourced rather than estimated, and what provenance accompanies the number. It does not cover failure modes (missing fixing, holidays, stale rate) or the exact return shape, which keeps it below 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.

Conciseness4/5

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

Two compact sentences with no filler, and the substantive purpose clause arrives immediately after the payment tag. The bracketed cost/x402 prefix occupies the very front of the description, pushing the actual purpose to second position, which is a minor structural flaw.

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

Completeness3/5

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

For a no-parameter, no-output-schema tool, the description should fully explain what comes back and in what convention. It does list the accompanying metadata (rate date, method, source attribution) but never states quote direction or precision for MYR/JPY, which is the main ambiguity an agent would face when interpreting 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 schema semantics are trivially complete; baseline is 4. The description's mention of rate date, method and source is return-value context rather than parameter meaning, so there is nothing extra to add.

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 the exact resource (MYR/JPY reference rate) and its provenance (latest ECB fixing, or official peg when JPY is pegged), which is more specific than the bare tool name. It does not explicitly distinguish itself from near-neighbours like fx_latest, fx_timeseries or fx_convert, but the single-pair scope is unmistakable.

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 this is the tool for a single spot MYR/JPY reference rate. There is no explicit when-to-use, no exclusion of alternatives (e.g. use fx_convert for converting an amount, fx_timeseries for history), and no note about what to do on a non-fixing day.

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