Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xaf_php

[PAID $0.002 USDC/call, x402, eip155:8453] Official XAF/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_xaf_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 well: it discloses the paid model ($0.002 USDC/call), the x402 protocol and chain (eip155:8453), the authoritative source (ECB), and the fallback behavior when PHP is pegged. It does not cover rate limits, failure modes, or caching/staleness beyond the rate date, which keeps it from a 5.

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 with no filler; every clause (payment, source, peg fallback, method, attribution) adds information. The bracketed payment/chain prefix sits ahead of the actual purpose, which slightly delays the core statement, but it is short enough not to impede scanning.

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?

There is no output schema, but the description compensates by enumerating what comes back: the rate, the rate date, the derivation method (direct, cross via EUR, or peg-derived), and source attribution. For a zero-parameter single-value lookup this is nearly complete; only the concrete response shape/field names are left implicit.

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 no parameter semantics to explain and the baseline is 4. The description correctly does not invent inputs and instead spends its words on the rate's provenance and derivation method.

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 a specific verb and resource: the official XAF/PHP reference rate from the ECB fixing. In a sibling set of hundreds of near-identical fx_<base>_<quote> tools, the pair is stated unambiguously and the data provenance (ECB) plus peg fallback further pins down which rate this is.

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 rather than stated: an agent can infer this is the tool for the XAF→PHP reference rate. There is no explicit guidance on when to prefer this over fx_convert, fx_latest, fx_timeseries, or the inverse fx_php_xaf, and no exclusions or prerequisites beyond the implicit payment requirement.

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