Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_jpy_sgd

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

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 supplied, the description carries the full burden and does well: it discloses the paid cost ($0.002 USDC/call via x402/eip155:8453), the data source (ECB fixing or official peg), the derivation method (direct, cross via EUR, peg-derived), and that results are deterministic with no estimation. It stops short of stating freshness/latency behavior on non-fixing days or what happens on failure.

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 plus a bracketed pricing tag; every clause (source, method, date, attribution, determinism) adds information. The cost/transport prefix is front-loaded ahead of the actual purpose, which is slightly suboptimal ordering but not wasteful.

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-input, no-output-schema rate lookup, the description covers what is returned conceptually (rate value, rate date, derivation method, source attribution) and the payment model. It could go further on response shape or stale-fixing handling, but nothing essential for correct invocation is missing.

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 clarify beyond the implicit pair encoded in the name. The baseline for a parameterless tool applies, with no deductions available.

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?

The description names the exact pair (JPY/SGD), the resource (official reference rate), and the specific source and vintage (latest European Central Bank fixing). An agent can distinguish it from fx_convert, fx_timeseries, or the inverse fx_sgd_jpy without opening anything else.

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 implied by the specificity of the pair and the word 'reference rate', but there is no explicit when-to-use guidance: nothing says to prefer fx_convert for conversion amounts, fx_timeseries for history, or fx_latest for a multi-pair snapshot. The agent must infer routing from the descriptions of siblings.

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