Skip to main content
Glama
verifystack-x402-mcp

verifystack-x402-mcp

Official

Multi-Chain DEX Liquidity & Order-Flow Oracle

verifystack_dex_market_intel
Read-onlyIdempotent

Fetch multi-chain DEX pool liquidity, 24h volume, price changes, and buy/sell order-flow data by token symbol or contract address to compare markets and assess trading pressure.

Instructions

Paid x402 API ($0.006 USDC on Base): Multi-chain DEX liquidity, 24h volume, price changes, and buy/sell order-flow oracle powered by DexScreener and GeckoTerminal.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verifystack_dex_market_intel"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoToken symbol or name query (e.g. AERO, VIRTUAL, PEPE)
chainNoOptional chain filter (base, ethereum, solana, arbitrum, bsc, polygon)
limitNoMax pools returned (1-30, default 10)
addressNoOptional token contract/mint address
minLiquidityUsdNoMinimum pool liquidity in USD (default 5000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. Addedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description is free to add the genuinely non-obvious behavior: this is a paid x402 endpoint charging $0.006 USDC on Base. That payment/pricing disclosure is operationally important and not available in any structured field. It stops short of 5 because it doesn't describe what happens on payment failure, rate limits, or response shape.

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?

A single dense sentence with zero filler, front-loaded with the cost/payment model the agent must know before calling. Every clause carries distinct information: pricing, chain scope, data domains, and data provenance.

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?

For a read-only, annotation-covered, no-output-schema tool with a fully documented schema, the description gives enough to call it correctly and to know what data domains come back. The notable gap is that all five parameters are optional, and the description never explains what the tool does when q, address, and chain are all omitted — a real ambiguity for invocation.

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 schema documents every parameter including the 1-30 limit range and the 5000 USD default liquidity floor, so the description need not repeat them. The only added meaning is thematic — 'liquidity' and 'order flow' map loosely to minLiquidityUsd and the returned data. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource set — multi-chain DEX liquidity, 24h volume, price changes, and buy/sell order flow — with named data providers (DexScreener, GeckoTerminal). An agent can distinguish this market-data tool from siblings like verifystack_token_safety or verifystack_defi_yields without opening the schema. It does not explicitly contrast with those siblings, which keeps it at 4 rather than 5.

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 implied by the enumerated data domains (liquidity, volume, order flow), and the paid x402 framing tells the agent there is a monetary cost to consider before calling. However, there is no explicit when-to-use/when-not-to-use statement and no pointer to an alternative for related questions (e.g., safety checks vs. market depth).

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