Trnch on Elysium

List a wallet's tokens with on-chain facts

trnch_scan_wallet

Read-onlyIdempotent

List the tokens a Elysium wallet holds in one call. Returns { wallet, truncated, partial, checked, tokens }: each token has address, symbol, name, balance { raw, decimals }, valueUsd when known, majorAsset, factsStatus and facts { sellTest, hookFee, liquidity, creator, launchpad, template, forcedTransfer } as in trnch_check, read for the 8 largest holdings that are not HYPE, WHYPE or USDC (others: factsStatus over_limit, call trnch_check). At most 100 tokens, largest first. Cached 60 s per wallet. Facts, not a verdict: Trnch runs no rug screen on this chain. No key needed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wallet": "<wallet>"
    },
    "name": "trnch_scan_wallet"
  }
}

Input Schema

Name	Required	Description	Default
`wallet`	Yes	Wallet address on Elysium (chainId 99901).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds what they cannot: 60-second per-wallet caching, a 100-token cap with largest-first ordering, truncation and partial flags, no API key needed, and the absence of any rug screen on this chain. These are operational traits an agent needs before deciding to call it.

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-loaded with purpose, then return shape, then limits and caveats – no wasted framing. The second sentence becomes a long run-on enumerating the facts object fields, which slightly hurts scanability.

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?

No output schema exists, so explaining the return shape (wallet, truncated, partial, checked, tokens and nested facts) is essential and done here. Coverage limits, the per-token over_limit behavior, and caching are all addressed, leaving no significant gap for an agent to call it correctly.

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?

There is a single required wallet parameter with full schema coverage (pattern plus chainId 99901 documented in the schema). The description adds no further semantics about the parameter itself, so the baseline 3 is appropriate.

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 verb and resource ('List the tokens a Elysium wallet holds in one call') with explicit scope limits (max 100, largest first). It is clearly distinguishable from trnch_check, which it names as the per-token facts tool.

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

Usage Guidelines5/5

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

Names the alternative and the exact condition that selects it: facts are only computed for the 8 largest non-HYPE/WHYPE/USDC holdings, and any other token with factsStatus over_limit should go to trnch_check. The 'facts, not a verdict' caveat also tells the agent not to treat this as a safety screen.

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?