Crypto Due Diligence

Screen a token for red flags

screen_token

Read-onlyIdempotent

Use this when the user gives a token address and asks "is this a rug?", "screen this coin", "who is the dev?" or what to check before buying. Pass chain (solana, ethereum, base, bsc, arbitrum, polygon, avalanche, optimism) and token (contract or mint address). Optionally pass github_url and deployer. Returns each signal as red_flag, keep_signal, not_seen or unknown, with a detail line and a source link, a reading (many_red_flags, some_red_flags or no_red_flags_seen), and the X links for a manual check. It reads public sources only and never says a token is safe. Not financial advice.

Input Schema

Name	Required	Description
`chain`	Yes	The chain the token lives on.
`token`	Yes	The token's contract address (0x...) or Solana mint address.
`deployer`	No	Optional wallet that launched the token, when GoPlus does not report one (most Solana tokens).
`github_url`	No	Optional GitHub account or repository to check, when the listing names none or a different one.

Output Schema

Name	Required	Description
`name`	No
`as_of`	Yes	ISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch.
`chain`	Yes
`token`	Yes
`notice`	Yes
`source`	Yes	Who the data comes from, to cite and to check it against.
`status`	Yes
`symbol`	No
`message`	No
`reading`	Yes
`signals`	Yes
`sources`	Yes
`unknown`	Yes
`x_links`	No
`pair_url`	No
`red_flags`	Yes
`incomplete`	Yes
`powered_by`	Yes
`keep_signals`	Yes
`token_age_days`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 19, 2026

addedOutput schema / properties / as_of / description

Added value: +"ISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch."

addedOutput schema / properties / source

Added value: +{
+  "description": "Who the data comes from, to cite and to check it against.",
+  "properties": {
+    "name": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "url"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "status",
-  "chain",
-  "token",
-  "reading",
-  "red_flags",
-  "keep_signals",
-  "unknown",
-  "incomplete",
-  "signals",
-  "sources",
-  "powered_by",
-  "as_of",
-  "notice"
-]New value: +[
+  "status",
+  "chain",
+  "token",
+  "reading",
+  "red_flags",
+  "keep_signals",
+  "unknown",
+  "incomplete",
+  "signals",
+  "sources",
+  "powered_by",
+  "as_of",
+  "notice",
+  "source"
+]

First observedOct 16, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations cover safety (readOnly, idempotent, non-destructive) and open-world reads, and the description adds materially more: it discloses the exact signal vocabulary (red_flag, keep_signal, not_seen, unknown), the overall reading values, that sources are public-only, and that the tool will never assert a token is safe. That 'never says safe' caveat is real behavioral context an agent could not infer from annotations.

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 the trigger condition, then inputs, then outputs, then the disclaimer. Slightly dense with the parenthetical chain list and the user-quote examples, but every element carries real selection information.

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?

Covers trigger, inputs, optional-input conditions, return shape by category, and the safety disclaimer, and an output schema exists so return details need not be enumerated. Nothing an agent needs to call this correctly 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 description coverage is 100% and the chain enum is already enumerated in the schema, so the description's restatement of the chain list adds little. It does clarify the optional-field usage conditions, but that is also stated in the schema descriptions, so the baseline of 3 is right.

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 ('screen a token'), and maps directly onto the user utterances that should trigger it ('is this a rug?', 'screen this coin'). It is clearly distinct from the wallet/feedback siblings.

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?

Gives explicit trigger conditions (user supplies a token address and asks about rug risk or the dev) and explains when to supply the optional github_url and deployer (when the listing names none or a different one). No alternative tool competes for this job, so nothing is left to inference.

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

All Crypto Due Diligence 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.