Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sar_jpy

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description supplies substantial operational detail: a $0.002 USDC charge per call, x402 payment on eip155:8453, deterministic non-estimated output, source attribution, and direct, EUR-cross, or peg-derived calculation methods. It does not cover fixing-day freshness, stale-rate behavior, or failure handling, so it is strong but not exhaustive.

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?

The payment prefix is compact, and the main sentence efficiently presents the currency pair, source, returned metadata, and methodology. The parenthetical about JPY being pegged is low-value for this specific pair, while 'Deterministic, sourced, no estimate' is dense shorthand that partly repeats the provenance already stated.

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-argument lookup without an output schema, the description covers invocation cost, latest-rate scope, provenance, derivation methods, and the principal metadata returned. Explicit quote orientation, behavior between ECB fixings, and guidance relative to the general-purpose FX siblings would remove the remaining ambiguity.

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 has zero parameters, so the zero-parameter baseline applies and there are no argument semantics left undocumented. The description also makes clear that this is a fixed latest-rate lookup rather than a lookup requiring a date, amount, or currency argument.

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 clearly identifies the resource as the latest official SAR/JPY reference rate and specifies its source, derivation methods, and accompanying metadata. Although it does not explicitly differentiate itself from fx_latest or fx_convert, the exact currency pair and official-reference scope make its purpose clear.

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?

The terms 'latest', 'Official', 'reference rate', and 'no estimate' establish a clear context: obtaining a current, authoritative SAR/JPY quote rather than an estimated rate. It does not explicitly route historical requests to fx_timeseries or amount-conversion requests to fx_convert, so it lacks full when-not and alternative-tool 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