Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_try_chf

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it discloses the paid x402 model at $0.002 USDC/call on eip155:8453, the data provenance (ECB fixing or official peg), the derivation method (direct, cross via EUR, peg-derived), and that no estimation is involved. It stops short of stating publication cadence or holiday/weekend behavior, which matters for a daily fixing.

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?

One dense sentence plus a bracketed pricing prefix. Every clause earns its place: resource, source, fallback behavior, returned metadata, and the deterministic guarantee. Core purpose is front-loaded after the payment tag.

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-parameter, no-output-schema tool, the description covers what is returned (rate, rate date, method, source attribution) and the payment requirement. The only meaningful gap is freshness semantics for an ECB fixing, which an agent would want before trusting a cached value.

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 nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies the call is parameterless by fixing the pair in advance.

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: 'Official TRY/CHF reference rate: latest European Central Bank fixing'. The pair is encoded in the name and confirmed in the text, so an agent can distinguish it from the hundreds of sibling pair tools. It does not, however, say anything about how it differs from general siblings like fx_latest, fx_convert 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 Guidelines3/5

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

Usage is only implied: an agent infers 'call this to get the TRY->CHF rate'. There is no explicit statement of when to prefer this over fx_latest, fx_convert or fx_timeseries, and no exclusions (e.g. 'do not use for historical series').

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