Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_gbp_php

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full load, and it does add real value: the per-call price (0.002 USDC, x402, eip155:8453), the source (ECB), determinism, and the fact that no estimation occurs. What it omits is behavior an agent still needs — whether weekday/holiday handling means a stale rate date, what a payment failure returns, and whether responses are cached.

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?

Two tight sentences with no filler, and the phrase 'Deterministic, sourced, no estimate' usefully front-loads the trust guarantee. The payment/billing metadata leads the description and is dense (USDC, x402, eip155:8453), but it is materially relevant since calling the tool spends money.

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 does the right work by enumerating what comes back: the rate, the rate date, the derivation method (direct, cross via EUR, peg-derived), and source attribution. Given a parameterless, annotation-free tool, that is nearly complete; only error/freshness behavior remains 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 there is no schema semantics for the description to compensate for; per the baseline for a 0-parameter tool, a 4 applies. The description correctly avoids discussing inputs, though it also does not clarify that the pair is fixed rather than selectable, which a sibling-heavy namespace might warrant.

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 resource and scope: the 'Official GBP/PHP reference rate', the 'latest European Central Bank fixing', and the fallback ('the official peg when PHP is pegged'). The currency pair in the name plus the stated source and derivation method let an agent distinguish this from the hundreds of sibling fx_XX_YY pairs without opening a schema.

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 single-pair reference-rate lookup for GBP/PHP. There is no explicit routing advice despite the presence of fx_convert (amount conversion), fx_latest (multi-pair latest), and fx_timeseries (history), all of which an agent could confuse with this tool.

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