Skip to main content
Glama

x402-services

by ai.firmbrain

sol_launches

Freshest Solana token launches from pump.fun: newest coins with age (seconds), USD market cap, SOL raised on the bonding curve, reply count, live flag, and socials. Send { limit?, maxAgeMin?, minMcapUsd? }. The real-time new-token radar for Solana sniper agents — pair with sol/rug-check before aping. [x402 paid tool — price $0.005; POST /api/sol/launches]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax coins, default 20 (max 50)
maxAgeMinNoOnly coins younger than this many minutes
minMcapUsdNoMinimum USD market cap filter

TDQS

A4.1/5.0
Behavior4/5

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

No annotations provided, so description shoulders full burden. Mentions paid tool and price, but lacks details on rate limits, idempotency, or side effects. However, as a read-only list tool, the behavioral traits are adequately implied.

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

Conciseness4/5

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

Two concise sentences plus a parameter list in parentheses. Efficient and front-loaded with key purpose, though includes some marketing language.

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?

No output schema but description lists returned fields (age, market cap, etc.). Parameters are well-documented. Sufficient for a filtered-list tool with clear filtering options.

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?

Input schema has 100% coverage with clear descriptions for all three parameters. The description lists parameters in parentheses but adds minimal extra meaning beyond the schema.

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?

Description clearly states the tool provides 'Freshest Solana token launches from pump.fun' and enumerates returned data fields. Distinguishes from siblings like sol_rug_check and sol_graduating.

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

Usage Guidelines4/5

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

Explicitly frames as 'real-time new-token radar for Solana sniper agents' and suggests pairing with sol/rug-check. Implicitly defines when to use, though lacks explicit when-not-to-use or alternatives.

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

All x402-services toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation4/5

Tools are organized by domain prefix (e.g., 'crypto_', 'rh_', 'snipe_'), which helps distinguish between areas. Within each domain, they serve distinct purposes, though some overlap between domains exists (e.g., price data appears in multiple groups). Overall, an agent can navigate effectively.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with a domain prefix and a verb_noun combination (e.g., 'compliance_risk', 'rh_stock', 'snipe_honeypot'). This makes the API predictable and easy to explore.

Tool Count2/5

With 159 tools, the server is extremely large. While the broad scope of web3 and utility functions justifies many tools, the count is significantly above the typical range for a coherent toolkit, potentially overwhelming agents and increasing selection error.

Completeness4/5

The toolkit covers a wide range of web3 operations: crypto, DeFi, compliance, safety, scheduling, memory, etc. There are no obvious major gaps for its intended purpose, though some niche areas might be missing.

Resources