Provides real-time pre-execution DEX liquidity metrics, volume, and risk indicators for Solana and crypto tokens, optimized for automated trading bots.
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlap. An agent can immediately tell what it does.
The single name uses clear snake_case with descriptive components (token_safety_scanner). With only one tool there is no pattern to verify, but the name itself is well-formed and self-explanatory.
One tool for an entire 'Intelligence Node' is thin; the full surface is a single scanner call. It earns its place, but there is no supporting operation to make the server more than a one-shot check.
The surface covers only a single point-in-time scan; there is no batch checking, historical liquidity tracking, holder/distribution analysis, or comparison across tokens. An agent needing ongoing or multi-token risk intelligence will hit a dead end.
Checks real-time DEX liquidity, trading volume, and pre-execution risk indicators for any token mint address.
| Name | Required | Description | Default |
|---|---|---|---|
| mint_address | Yes | Token mint address or contract identifier. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It does not state whether the operation is read-only, whether it hits on-chain data or an indexer, what latency or rate limits apply, or how fresh 'real-time' data actually is. Only the general subject matter is disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler; every clause identifies a distinct check performed. Nothing can be trimmed without losing information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter read tool this is minimally adequate, but with no output schema and no annotations the description should explain what the risk indicators look like or what a caller receives. The omission of return-value and safety context leaves a real gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the single mint_address parameter is already documented. The description adds only that any token mint address is accepted, which is marginal beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Checks') and names concrete resources: real-time DEX liquidity, trading volume, and pre-execution risk indicators, scoped to a token mint address. It is clear what the tool does, though there are no sibling tools to differentiate from.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'pre-execution risk indicators' implies usage before executing a trade, but the description never states when to use this tool versus alternatives, nor any exclusions or prerequisites. Usage is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
token_safety_scanner
Add one secure layer between your agents and this server.