Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

scan_dex_token_security

Read-onlyIdempotent

Scan DEX token pairs on Solana, Ethereum, Base, Arbitrum, and BSC for honeypots, mint/freeze authority, buy/sell taxes, and liquidity locks; return audited pairs with risk levels and flags.

Instructions

Scan decentralized exchange (DEX) token pairs across Solana, Ethereum, Base, Arbitrum, and BSC using DexScreener and GoPlus Security APIs to detect honeypots, mint/freeze authority, buy/sell taxes, and liquidity locks. Returns audited token pairs with riskLevel and security flags.

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": {
      "searchQuery": "<searchQuery>"
    },
    "name": "scan_dex_token_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainIdNoTarget blockchain network identifier.solana
maxResultsNoMaximum number of audited token records to return (1 to 100).
searchQueryYesToken ticker symbol (e.g., SOL, PEPE), token name, or smart contract address to audit.SOL
minLiquidityUsdNoMinimum DEX pool liquidity threshold in USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the description is not burdened with safety disclosure. It nonetheless adds real value by naming the upstream data sources (DexScreener and GoPlus Security) and stating that only audited pairs with riskLevel and security flags come back, which explains why some tokens may be absent. Minor gap: the chain list omits polygon even though the schema enum includes it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with the capability, chain scope, data sources, and return shape front-loaded; no filler or restatement of the title. The enumerated threat list earns its space by telling the agent what the output can be used to decide.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does the necessary work of describing the return shape (audited pairs with riskLevel and security flags). It falls short on edge behavior an agent would want: what happens when a token is not audited or not found, and the discrepancy between the five chains named and the six in the enum.

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%, so every parameter (chainId, maxResults, searchQuery, minLiquidityUsd) is already documented with defaults and bounds. The description adds no further semantics about accepted query forms or how the liquidity filter interacts with results, so the baseline 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?

The description names a specific verb (Scan) and a precise resource (DEX token pairs), then enumerates the chains covered and the exact threat classes detected (honeypots, mint/freeze authority, buy/sell taxes, liquidity locks). No sibling tool in the list overlaps this resource, so an agent can identify it immediately from the name plus description.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is for pre-trade or due-diligence token vetting, but the description never states when to choose it, when not to, or how it relates to adjacent tools such as screen_wallet_aml_risk. No prerequisites, rate-limit caveats, or exclusions are given.

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