Trnch on Elysium

Top Elysium tokens by 24-hour volume

trnch_top_volume

Read-onlyIdempotent

The tokens of the Elysium pools with the most trading volume over the last 24 hours, in the order GeckoTerminal lists them (the Top volume list of Trade on Trnch), with a link to trade each. HYPE, WHYPE and USDC are left out. Returns { tokens [{ rank, address, symbol, name, logoUrl, trade }] }, no volume figures. A volume ranking, not a screen, a verdict or a recommendation: 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_top_volume"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many tokens (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses the exclusion of HYPE, WHYPE and USDC, that results contain no volume figures despite being a volume ranking, that ordering follows GeckoTerminal, and that no API key is required. These are exactly the behavioral facts an agent could otherwise get wrong.

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?

Front-loads the core definition, then the exclusions, then the return shape, then the caveat. Slightly dense with the parenthetical '(the Top volume list of Trade on Trnch)', but every sentence adds a distinct fact.

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?

With no output schema, the description supplies the return shape inline ({ tokens [{ rank, address, symbol, name, logoUrl, trade }] }) and warns that volume figures are absent. For a one-parameter read tool, nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter has 100% schema coverage including default, min and max, so the schema carries the meaning. The description never mentions the limit or how truncation interacts with the ranking, adding nothing beyond structured data — baseline 3.

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 resource and scope: tokens of Elysium pools ranked by 24-hour trading volume, in GeckoTerminal's ordering, with excluded symbols named. An agent can distinguish this from trnch_check because the description explicitly says it is a ranking and not a screen.

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?

Clearly frames when this tool applies (wanting the top-volume list with trade links) and, via 'Trnch runs no rug screen on this chain', implies the screening alternative without naming it. It does not give an explicit 'use trnch_check instead when...' routing statement, so it stops short of a 5.

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?