Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_php_sar

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description does real work: it discloses the $0.002 USDC/call x402 payment, the settlement network (eip155:8453), the data provenance (ECB fixing), the peg fallback, and the returned method classification. It still omits practical behavior an agent needs, such as how the x402 payment handshake is triggered and what happens on payment failure, so the disclosure is above baseline but incomplete.

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 cost prefix; every clause (rate, date, method, attribution, no-estimate) adds information. The payment metadata is front-loaded ahead of the purpose, which slightly delays the core subject but is defensible for a paywalled tool.

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 and no annotations, the description compensates well by enumerating the returned fields (rate, rate date, method, source attribution) and the pricing model. The gap is the x402 payment mechanics, which an agent must know to actually complete a paid call.

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 and the baseline is 4. The description correctly presents this as a parameterless single-pair lookup rather than inviting options.

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 (Official PHP/SAR reference rate), its source (latest European Central Bank fixing), and the fallback (official peg when SAR is pegged), which is enough to distinguish it from the other fx_* pair tools. It stops short of explicitly naming alternatives such as fx_convert or fx_latest, and no verb frames the retrieval action, so the purpose is clear but not maximally differentiated.

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: the pricing bracket and the claim 'no estimate' signal a paid, authoritative source suitable when a deterministic official rate is required. There is no explicit when-to-use/when-not guidance and no pointer to fx_convert for conversions or fx_timeseries for history.

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