Trnch on Elysium

Trnch on Elysium: chain, routers, fees and activity

trnch_stats

Read-onlyIdempotent

Read the facts of Trnch on Elysium: chainId 99901, gas HYPE, reference stable USDC, the three routers (Uniswap, KyberSwap and LI.FI), the bot fee grid in percent, and activity { windows [{ window (24h, 7d, 30d), volumeUsd, swaps, traders }] } counted from swaps made through Trnch on this chain (null while hidden or unavailable). No Heat and no rug counts: Trnch runs no rug screen on this chain. No key needed.

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": "trnch_stats"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: fields are 'null while hidden or unavailable', there is no rug screen on this chain, and 'No key needed' removes an auth question an agent would otherwise have to resolve.

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?

One dense but front-loaded sentence carrying the most decision-relevant facts first (chain, gas token, routers, fees), followed by the activity shape and scope exclusions. The inline `{ windows [{ window ... }] }` notation is slightly awkward to parse but earns its place given there is no output schema.

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?

Without an output schema the description must carry the return shape, and it does so for the activity block (window, volumeUsd, swaps, traders) plus null semantics. It leaves the fee grid's internal structure and the meaning of 'Heat' undefined, which is a modest gap for a zero-parameter read tool.

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; per the baseline this dimension starts at 4. The description instead spends its words on outputs, which is the right allocation.

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 verb and resource ('Read the facts of Trnch on Elysium') and then enumerates the exact contents: chainId 99901, gas token HYPE, reference stable USDC, three named routers, bot fee grid, and activity windows. It also carves out negative scope ('No Heat and no rug counts'), which sets it apart from a screening tool, though it never names a sibling explicitly.

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 can infer this is the metadata/statistics call to make before quoting or trading, but the description never says 'use this first' or 'use trnch_top_volume instead for ranking'. No prerequisites, no exclusions beyond the rug/Heat note.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Trnch on Elysium tools Inspect

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

Need Help?