Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sar_php

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

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 real work: it discloses the paid cost ($0.002 USDC/call), the x402 protocol, the settlement network (eip155:8453), and non-obvious data behavior — ECB sourcing, peg fallback, and that the method (direct/cross via EUR/peg-derived) is reported. It stops short of explaining the payment handshake or caching/freshness cadence.

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?

Front-loaded with the payment terms, then the substantive rate semantics, then a short trust clause. Every clause carries information; the single long sentence is dense but not padded.

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?

With no output schema, the description usefully enumerates what comes back (rate, rate date, method, source attribution), and it covers sourcing and fallback logic. The only gap for an agent is the mechanics of satisfying the x402 payment, which the description flags but does not explain.

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 disambiguate beyond confirming that the pair is fixed. Baseline of 4 applies for a parameterless tool.

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 resource (SAR/PHP reference rate), a specific source (latest European Central Bank fixing), and the fallback semantics (official peg when PHP is pegged). Against hundreds of sibling fx_* pair tools the pair is unambiguous, and 'reference rate' vs 'convert' distinguishes it from fx_convert.

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 pair name and the 'reference rate' framing, so an agent knows this returns a rate rather than performing a conversion. However, it never names alternatives such as fx_convert (for actual conversion), fx_timeseries (historical), or fx_latest, nor does it state prerequisites like an x402 wallet or payment.

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