Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_sgd_chf

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

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 supplied, the description carries the behavioral burden well by disclosing the exact per-call price, USDC currency, x402 payment mechanism, and chain identifier. It also explains determinism, source attribution, and calculation methods, though it does not explicitly state read-only behavior or describe fixing availability and potential staleness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The compact payment prefix is followed by a dense but readable statement of scope, source, fallback, outputs, and reliability. Nearly every phrase supplies actionable information, with only minor repetition between 'source attribution' and 'sourced'.

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-argument lookup without an output schema, the description usefully covers the rate, rate date, calculation method, attribution, determinism, and payment requirements. It remains missing explicit sibling-selection guidance and operational details such as rate units beyond the SGD/CHF convention, publication timing, or behavior when a fixing is unavailable.

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?

There are no parameters, so the baseline score of 4 applies. The fixed SGD/CHF wording helps explain why no arguments are needed, while the method and output details add useful meaning without requiring parameter documentation.

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?

The description clearly identifies a latest official SGD/CHF reference-rate lookup, naming the ECB fixing, peg fallback, and returned rate metadata. Its fixed pair and official, non-estimated scope provide some differentiation, but it does not explicitly distinguish itself from fx_convert, fx_latest, or fx_timeseries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Terms such as 'latest', 'official', 'Deterministic', and 'no estimate' establish a clear use case: retrieving the most recent sourced reference fixing rather than an estimated or historical value. However, there is no explicit routing to siblings for amount conversion, general latest-rate queries, or time-series requests.

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