Skip to main content
Glama
Sign In

TRNCH

by fun.trnch
OverviewDiscussionsAdmin

Is this token a rug? Trnch check

trnch_check
Read-onlyIdempotent

Check any Robinhood Chain token before you buy it: is it a rug, a honeypot, a scam or a copycat? Returns { status, category, rugged, dumped }: status kept_out (Trnch keeps it out of the Heat and will not trade it), in_heat, seen or unknown, with a public risk category (SCAM_CONTRACT, LINKED_TO_PAST_RUG, HEAVY_SELL_TAX, CANNOT_SELL, COORDINATED_LAUNCH, COPYCAT, LIQUIDITY_PULLED, DUMPED, OTHER_RISK; DUMPED is a coordinated dump, not a rug). unknown means not seen by Trnch, not a pass. No key needed. Also returns creator { history, tokensInHeat } or null: launch history of the token's creator (bucketed), context only, not part of the verdict. A signal, never a guarantee. Full record: https://trnch.fun/tia

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": {
      "token": "<token>"
    },
    "name": "trnch_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesToken contract address on Robinhood Chain (chainId 4663).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent read, yet the description adds substantial context beyond them: the exact return fields, the meaning of each status value, what 'kept_out' implies for trading, the full risk-category vocabulary, and the caveat that creator history is 'context only, not part of the verdict'. It also states no API key is required and qualifies the result as 'a signal, never a guarantee'.

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?

The verdict question and return shape are front-loaded, and nearly every clause carries information (status semantics, category vocabulary, creator caveat). The long parenthetical category list makes one sentence dense, but nothing is genuinely redundant.

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?

There is no output schema, so the description must explain the response, and it does: status values, risk categories, the creator object's shape and null case, and a link to the full record. For a single-parameter lookup, nothing an agent needs to call or interpret it 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?

Schema coverage is 100% and the token parameter already documents the address format, chainId 4663 and the hex pattern. The description adds no syntax or format information beyond the schema, so the baseline of 3 applies.

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?

Names a specific verb and resource ('Check any Robinhood Chain token') and frames the exact question answered ('is it a rug, a honeypot, a scam or a copycat'). The scope is distinct from siblings like trnch_scan_wallet or trnch_heat, so an agent can select it without opening a schema.

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?

'Check ... before you buy it' gives a clear usage moment and implicitly routes from the trading siblings. It also warns how to read a negative result ('unknown means not seen by Trnch, not a pass'), though it never names an alternative tool or states explicit exclusions.

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

All TRNCH 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