Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_php_usd

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 model ($0.002 USDC/call via x402 on eip155:8453), the authoritative source (ECB), the fallback behavior when USD is pegged, and that results are deterministic with no estimation. It omits error behavior, staleness bounds, and rate-limit details.

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 front-loaded sentence that puts the price and protocol first, then the data semantics. Every clause adds information (source, method, attribution, determinism), with only mild density from the parenthetical payment metadata.

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-parameter lookup with no output schema, the description covers what is essential: the value, its date, the derivation method, and provenance. An agent can invoke it correctly without further information; only freshness/staleness expectations are left unstated.

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 the baseline is 4; there is nothing in the schema that the description needs to compensate for. The description appropriately spends its limited space on the returned fields instead of nonexistent inputs.

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?

States a specific verb+resource: 'Official PHP/USD reference rate' from 'latest European Central Bank fixing', which tells an agent exactly what single value is returned. The currency pair is unambiguous, though the description never contrasts itself with sibling tools like fx_convert, fx_latest or fx_timeseries that touch the same data.

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?

'Latest ... fixing' and 'no estimate' imply this is for a single authoritative spot rate rather than historical series or conversion, giving implicit usage guidance. However, no alternative is named and no when-not-to-use condition is stated, so the agent must infer that fx_timeseries or fx_convert serve adjacent needs.

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