Skip to main content
Glama

FlowGate Launch Verdict

How to get the full paid Launch Verdict

how_to_buy_verdict
Read-onlyIdempotent

Free. Returns the URL, price ($0.01) and x402 payment details for the full Launch Verdict of a token or pool, and whether it is in the index. It does not pay or take any key; the caller pays with its own x402 client.

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

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

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely non-obvious behavior: the tool charges nothing, holds no key, takes no payment itself, and instead hands back pricing and x402 details for the caller to settle externally. That is meaningful context annotations cannot express.

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

Conciseness5/5

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

Two sentences, zero filler, and the most decision-relevant fact ('Free') is placed first. The second sentence cleanly separates what the tool does from what it deliberately does not do.

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 response, and it does list the returned elements: URL, price, x402 payment details, and index status. For a one-parameter lookup this is nearly sufficient; it stops short of describing the shape of the x402 payload itself, which an agent must forward.

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 formats (0x+40 hex address, 0x+64 hex v4 pool id) and points at recent_launches as the source. The description only echoes 'of a token or pool' without adding format or validation detail beyond the schema, so the baseline 3 is appropriate.

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 verb and payload: it returns the URL, price, and x402 payment details for the full Launch Verdict and whether the token/pool is indexed. That is far more specific than the name alone. It does not explicitly name launch_preview or recent_launches as alternatives, so sibling differentiation is only implied by the 'full paid' framing.

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?

The description makes the usage context clear in a cost sense: it is free, it does not pay, and the caller must settle with its own x402 client. What is missing is explicit routing guidance — when an agent should call this rather than launch_preview or recent_launches, and whether calling it is a prerequisite to obtaining the paid verdict.

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