Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_try_cny

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

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 per-call price, the payment protocol and chain (x402, eip155:8453), the data provenance (ECB fixing), and the determinism guarantee ('no estimate'). It omits operational details such as wallet/auth requirements for the x402 flow and rate-limit or caching behavior, which are relevant for a paid endpoint.

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 sentences, front-loaded with the payment/cost tag that matters before an agent commits to a call, followed by the data semantics. The trailing list ('rate date, method, source attribution') is dense but each item carries real information; nothing is filler.

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 lookup with no output schema, the description fully compensates by naming the returned components (rate, rate date, method, source attribution) and the possible methods (direct, cross via EUR, peg-derived). An agent knows what it will get and what it will pay before invoking.

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 semantics to explain; baseline is 4. The description correctly implies the pair and source are fixed by the tool identity rather than being arguments.

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 the exact resource ('Official TRY/CNY reference rate') and the exact source ('latest European Central Bank fixing'), so an agent can distinguish it from the hundreds of sibling fx_<base>_<quote> tools by the currency pair alone. It also qualifies the fallback case ('or the official peg when CNY is pegged'), removing ambiguity about what a TRY/CNY quote can mean.

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 the pair name and the phrase 'reference rate', but the description never says when to prefer this over fx_convert (amount conversion), fx_cny_try (the inverse pair), fx_latest, or fx_timeseries. A monetary-cost signal ('$0.002 USDC/call') hints that this is one call among many paid options, yet no explicit routing guidance is given.

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