Skip to main content
Glama

Plan an AI feature's road to launch

plan_ai_launch
Read-onlyIdempotent

A phased roadmap from where an AI feature is today to launch and its first month live: frame, prototype and model, evals, hardening, pilot, launch, monitoring. Each phase has exit criteria and the tests and checks for this feature, backed by findings from AI PM Lab's recorded real runs (injection, grounding, evals, agent cost). Returns instructions to follow with the user's text.

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

Input Schema

NameRequiredDescriptionDefault
featureNoWhat the AI feature does, who uses it, what it must never do, and where the work stands today

Output Schema

NameRequiredDescriptionDefault
textYesThe answer in markdown, as shown to the user; for the guides, instructions to follow with the user's text
linksYesThe AI PM Lab pages the answer links to, where each idea can be tried hands-on

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety needs no restating. The description adds genuinely non-obvious behavior: it returns *instructions to follow with the user's text* rather than a finished plan, and its content is grounded in recorded real runs from AI PM Lab. That tells the agent to expect a prompt-like payload, not an analysis.

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?

The core framing is front-loaded in the opening clause, and the phase enumeration earns its length by telling the agent what the roadmap contains. The single long sentence is dense but each clause carries information; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. What remains for the description is scope, phase coverage, provenance, and the key fact that it returns instructions rather than results – all present. Nothing an agent needs in order to call this correctly is missing.

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 description coverage is 100% and there is a single optional parameter, so the schema already carries the burden. The description refers to 'this feature' but adds no guidance beyond the schema's own wording about what to include (scope, users, prohibitions, current state). Baseline 3 applies.

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 concrete verb and resource: a phased roadmap from the feature's current state through launch to first-month monitoring, with the phases enumerated in order. It is clear what the tool produces. It stops short of naming the nearest siblings (review_launch_readiness, design_eval_suite) so the agent must infer the boundary itself.

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 only implied: the phrase 'from where an AI feature is today to launch' signals the planning-ahead scenario. There is no explicit when-to-use, no when-not-to-use, and no pointer to the alternative tools for readiness review or eval design that overlap this roadmap.

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