Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_php_gbp

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does substantial work: it discloses the per-call price and payment mechanism ($0.002 USDC via x402 on eip155:8453), the data source (ECB fixing), the derivation method (direct, cross via EUR, or peg-derived), and that values are not estimates. It does not cover publication lag/freshness or what happens when no fixing exists for the date.

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 leads with the pricing/access constraint and then the substantive definition, with no filler. It is dense but every clause (source, peg fallback, method, determinism) conveys distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with no output schema, the description does outline the returned fields (rate, date, method, attribution), which is helpful. However, it never resolves the quote direction of 'PHP/GBP' (PHP per GBP vs GBP per PHP), a critical ambiguity for a rate tool, and says nothing about fixing freshness or a no-fixing case.

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 meaning to add; baseline applies. The description instead clarifies what is fixed for the caller (the pair) and what varies in the response (rate date, method, attribution).

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 resource and scope: the official PHP/GBP reference rate, sourced from the ECB fixing, with peg fallback. The currency pair is unambiguous from name plus description, so an agent can pick it out of the huge fx_* family without opening the (empty) schema. It stops short of naming sibling routes like fx_convert or fx_timeseries for related needs.

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 by qualities ('deterministic, sourced, no estimate'), which signals 'use when you need an authoritative published rate' rather than a computed conversion. There is no explicit when-to-use/when-not clause and no pointer to fx_convert, fx_latest, or fx_timeseries for historical or cross-pair needs, despite those siblings existing.

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