Skip to main content
Glama

sol_safe_launches

Read-onlyIdempotent

Fresh pools + a built-in clean/risky/danger screen — poll it, skip the rugs — The fresh-launch feed with a safety screen built in: the newest Solana pools (incl. pump.fun), each tagged clean / risky / danger from a fast mint-level check — mint & freeze authority renounced, and Token-2022 seize extensions (permanent-delegate, transfer-hook, non-transferable, frozen-by-default). Poll it to skip the obvious rugs, then run sol-pre-trade-gate on the ones you like. Optional: limit (1–20), minLiquidityUsd. No feed → not charged. Not advice. Priced $0.06 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.

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": "sol_safe_launches"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax pools (1–20)
minLiquidityUsdNoMin liquidity USD

Output Schema

NameRequiredDescriptionDefault
dataNoThe result payload. Shape is service-specific; every field is documented in the tool description.
serviceNoThe service id that answered.
checkedAtNoISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, and the description adds substantial context beyond them: the exact screen criteria (mint & freeze authority renounced, permanent-delegate, transfer-hook, non-transferable, frozen-by-default), that no-feed responses are not charged, and the payment model. It stops short of describing refresh cadence or how stale a 'fresh' pool can be.

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

Conciseness3/5

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

The purpose is front-loaded, but the opening is a redundant fragment ('Fresh pools + a built-in clean/risky/danger screen — poll it, skip the rugs') immediately restated by the next clause describing the same thing. Pricing, disclaimer, and auth boilerplate pad the tail without helping tool selection.

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 an output schema present, return values needn't be explained; the description covers screening semantics, cost/auth requirements, and the next-step tool. For a two-parameter read-only feed, this is close to complete, missing only feed recency/freshness definition.

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 coverage is 100% and both parameters carry their own descriptions ('Max pools (1–20)', 'Min liquidity USD'). The description only restates 'Optional: limit (1–20), minLiquidityUsd' without adding units, defaults, or behavior (e.g., what happens when minLiquidityUsd excludes everything), so the schema does the work.

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?

States a specific resource and scope: the newest Solana pools (including pump.fun), each tagged clean/risky/danger via a mint-level authority and Token-2022 extension screen. An agent can tell this apart from sol_new_pairs (raw feed) and sol_pre_trade_gate (deeper per-token check) without opening any schema.

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?

Gives explicit usage flow: 'Poll it to skip the obvious rugs, then run sol-pre-trade-gate on the ones you like', which names the downstream alternative and the condition for escalating. It does not state when to prefer or avoid it relative to the closest sibling, sol_new_pairs, so the routing is clear but not fully exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources