Verifies DEX LP token locking, vesting schedules, pool liquidity depth, and unwrap risks across Aerodrome and Uniswap. Cost: 0.020 USDC on Base & Solana Mainnet.
| Name | Required | Description | Default |
|---|---|---|---|
| token_address | Yes | Target ERC-20 contract address on Base (0x...) or Solana SPL Mint |
| Name | Required | Description | Default |
|---|---|---|---|
| pools | Yes | Breakdown of verified pools by DEX venue | |
| total_liquidity_usd | Yes | Sum of verified pool reserves converted to USD |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "pools": {
+ "description": "Breakdown of verified pools by DEX venue",
+ "items": {
+ "properties": {
+ "dex": {
+ "type": "string"
+ },
+ "liquidity_usd": {
+ "type": "number"
+ },
+ "pool_address": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "total_liquidity_usd": {
+ "description": "Sum of verified pool reserves converted to USD",
+ "type": "number"
+ }
+ },
+ "required": [
+ "total_liquidity_usd",
+ "pools"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, openWorld, non-destructive, so safety is covered. The description adds genuinely useful operational context beyond that: the tool is paid (0.020 USDC) and runs on Base and Solana Mainnet, which affects invocation planning. It stops short of noting latency, rate limits, or payment failure behavior.
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?
Two tight sentences: capability and scope first, cost/chains second. No filler, and the most decision-relevant information is front-loaded.
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?
Output schema exists, so return values need not be described. Between the description (scope, DEXs, chains, cost) and annotations (read-only, open-world), an agent has enough to call it correctly; only explicit sibling disambiguation is missing.
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?
There is a single parameter with 100% schema description coverage, so the schema already carries the semantics; baseline 3 applies. The description reinforces supported chains but adds no new format or validation detail.
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?
States a specific verb ("Verifies") and enumerates the exact resources checked: LP token locking, vesting schedules, liquidity depth, unwrap risks, plus named DEXs (Aerodrome, Uniswap). However, it does not distinguish itself from the sibling rugshield_audit_liquidity_lock_verify, which appears to cover overlapping ground.
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?
Scope (Aerodrome/Uniswap, Base & Solana) implies when the tool applies, but there is no explicit when-to-use guidance, no exclusions, and no routing to the near-duplicate liquidity-lock sibling. The agent must infer selection from the description alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.