Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_xof_aed

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 price and payment protocol ("PAID $0.002 USDC/call, x402, eip155:8453"), the data source (ECB), determinism, and that it is a published fixing rather than an estimate. It omits edge behavior such as what is returned on weekends/holidays when no fixing is published.

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 cost gate, then the resource, then the returned fields. The closing "Deterministic, sourced, no estimate" is slightly redundant reassurance but short enough to justify itself as a trust cue.

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

Completeness5/5

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

For a zero-parameter, read-only rate lookup with no output schema and no annotations, the description covers what an agent must know before calling: the pair, the source, the cost and payment scheme, and the fields accompanying the rate (date, method, attribution). Remaining gaps like exact response shape are minor at this complexity.

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; both currencies are baked into the tool identity and the description adds no parameter confusion. No parameter meaning needs explaining beyond what exists.

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?

States a specific verb-and-resource combination: 'Official XOF/AED reference rate', with the underlying source named (ECB fixing / official peg). The pair is explicit in both the name and the description, so an agent can distinguish it from the hundreds of sibling fx_* pair tools without opening the 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 by 'latest ... fixing', which signals a single current snapshot rather than a series, but the description never names alternatives such as fx_timeseries (historical) or fx_convert (conversion) or fx_latest. In a sibling set this large, explicit routing guidance would materially help.

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