Skip to main content
Glama

Ballistic

Launch limits

get_limits
Read-onlyIdempotent

The limits Ballistic enforces for one launchpad and pair: how many wallets hold the supply after a launch, holder wallets and each one’s share of supply, wallets in the launch itself, supply range, largest buy, per mode (Block-0 and Reserve). Call list_launchpads_and_pairs first for the launchpad ids. An unknown launchpad is refused. Read-only.

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": {
      "venue": "<venue>"
    },
    "name": "get_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairNoWhat the token is paired with, for example SOL, USDC or a stock symbol. Omit for the chain’s own coin.
venueYesLaunchpad id or name: pumpfun, stonkfun, flap or pons.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so 'Read-only' is redundant. What the description adds is genuinely beyond the annotations: the refusal behavior on unknown launchpads, the required lookup call ordering, and a field-level account of what the response contains (including that limits differ by Block-0 and Reserve mode).

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?

Scope and the enumerated contents are front-loaded in the first sentence, followed by short imperative sentences for the prerequisite and the error case. The opening sentence is dense and list-like, but every clause carries information an agent needs; nothing is padding.

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 output schema, the description carries the burden of describing the return payload, and it does so at a useful level of granularity. It also covers the prerequisite lookup and the unknown-venue failure path. The only gap is minor ambiguity about whether both modes are always returned or selected somewhere.

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 the schema already explains both `pair` (omit for the chain's own coin) and `venue` (launchpad id or name, with examples). The description restates 'one launchpad and pair' without adding format, casing or resolution rules, so it hovers at the baseline. The 'per mode (Block-0 and Reserve)' phrase refers to a returned dimension, not an input, and is not clearly tied to either parameter.

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 limits Ballistic enforces for one launchpad and pair') and then enumerates exactly what those limits cover: post-launch holders, per-holder share, launch wallets, supply range, largest buy, split per mode. That level of specificity separates it cleanly from siblings like get_features, get_pricing and estimate_fee.

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 an explicit prerequisite ('Call list_launchpads_and_pairs first for the launchpad ids') and an explicit failure condition ('An unknown launchpad is refused'), which is real routing guidance. It does not name any alternative for adjacent questions (fees, features), so it stops short of full when/when-not coverage.

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