Skip to main content
Glama

Ballistic

Launchpads and pairs

list_launchpads_and_pairs
Read-onlyIdempotent

The launchpads Ballistic launches on today, with chain, gas coin, launch modes, who can use them, and what each can be paired with (for example SOL or USDC on pump.fun, a tokenised stock on StonkFun). Includes the live size of the pair lists when they can be read. Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds value beyond them by enumerating the fields returned (chain, gas coin, launch modes, access, pairings) and by disclosing that pair-list sizes are included only 'when they can be read' — a genuine caveat that partial or degraded results are possible. There is no output schema, so this field enumeration carries real weight; only pagination/ordering behaviour remains undisclosed.

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?

A single dense sentence front-loads what is returned, followed by a short tag 'Read-only.' that reinforces safety. Every clause adds information (fields, examples, data-availability caveat), though the parenthetical examples make the sentence long and slightly harder to scan than a short bulleted field list would be.

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 parameters and no output schema, the description must carry the return-shape burden, and it does so by naming the attributes of each launchpad and its pairings. The data-availability caveat covers the main behavioural risk; minor gaps are result ordering and whether the list is capped, which are unlikely to block a correct call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is an empty object with additionalProperties false, consistent with the description's parameter-free nature.

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 states a concrete scope: launchpads launching today, with chain, gas coin, launch modes, access rules, and supported pairings, giving two worked examples (SOL/USDC on pump.fun, a tokenised stock on StonkFun). That is far more specific than the title alone and clearly separates it from siblings like get_pricing or estimate_fee. It falls short of 5 only because it never uses an explicit listing verb or frames the output as a collection, leaving the agent to infer it is a retrieval of all current launchpads.

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 temporal scope ('today') and the read-only framing, so an agent can tell this is a current-state lookup rather than a historical query. However, there is no explicit statement of when to prefer this over siblings such as get_features or compare_with, and no prerequisites 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources