boo-x402-mcp

Overview Schema Source Related Servers Discussions Admin

Discover trending meme tokens

meme_discover

Discover trending and newly launched meme tokens on a specified blockchain. Use to identify hot tokens before conducting further research.

Instructions

Find meme tokens that are trending / newly launched right now on a chain. Use to see what is hot before picking a token to research.

PAID TOOL: up to $0.01 USDC per call (x402 on Base). Paid automatically from your configured wallet.

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": {
      "chain": "<chain>"
    },
    "name": "meme_discover"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	Yes	Chain: eth, bnb, base, solana.
`limit`	No	Max results.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 11, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Since annotations are absent, the description reveals an important behavioral trait—the tool is paid (up to $0.01 USDC per call). No other side effects are mentioned, but the cost disclosure is valuable.

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?

The description is extremely concise: two sentences plus a payment note, with the core purpose front-loaded. No wasted words.

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

Completeness3/5

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

The description lacks any information about the return value or output format, which would be helpful. However, given the tool's simplicity and the 100% schema coverage, the missing output info is a minor gap.

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?

The schema covers 100% of parameters with descriptions. The tool description adds no additional parameter information beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 clearly states it finds meme tokens that are trending or newly launched, with a clear purpose: to see what is hot before research. However, it does not explicitly distinguish itself from sibling tools like meme_signal.

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?

The description provides a typical use case (see what is hot before researching), but lacks explicit when-not-to-use or alternatives among siblings.

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