Skip to main content
Glama

FlowGate Launch Verdict

Free preview of a new pool's on-chain flags

launch_preview
Read-onlyIdempotent

Free, rate limited. For a pool in the launch index: a label from pool events only (swaps, liquidity changes, price moves) and counts of high, medium and info flags. No flag text, token-contract checks or precedent; the paid verdict has those. On-chain facts only: not a safety check, audit or forecast.

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": {
      "token_or_pool_id": "<token_or_pool_id>"
    },
    "name": "launch_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
token_or_pool_idYesToken address (0x + 40 hex) or Uniswap v4 pool id (0x + 64 hex), as listed by recent_launches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses cost and throttling ("Free, rate limited"), states the evidential basis ("pool events only", "on-chain facts only"), and enumerates what the response deliberately excludes. That is exactly the kind of operational context annotations cannot carry.

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?

Front-loaded with cost and throttle, then scope, then payload, then exclusions — dense and waste-free. The telegraphic sentence fragments ("No flag text, token-contract checks or precedent;") trade some readability for brevity.

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 does the work of describing the return shape (label plus counts) and its limits, which is adequate for a one-parameter read. It leaves the set of possible label values unstated, so an agent cannot anticipate the response vocabulary.

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 single parameter already documents both accepted address formats and points at recent_launches as the source. The description reinforces scope ("a pool in the launch index") but adds no new syntax or format meaning beyond the schema.

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?

States a specific verb/resource (preview of on-chain flags for a pool in the launch index) and enumerates the payload: an event-derived label plus high/medium/info flag counts. It signals the boundary with the deeper paid verdict ("the paid verdict has those") without naming the sibling how_to_buy_verdict, so differentiation is inferable but not explicit.

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?

Clear about applicability ("for a pool in the launch index") and explicitly points to a richer alternative for what this tool omits (flag text, token-contract checks, precedent). It also sets exclusions ("not a safety check, audit or forecast"), though it never names the sibling tool or states a trigger condition for choosing the paid path.

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