Skip to main content
Glama

Review an AI feature's launch readiness

review_launch_readiness
Read-onlyIdempotent

A go/no-go review of an AI feature's launch plan: evals, grounding, attacks, approvals, cost, latency, monitoring, rollout and support, each marked ready, at risk or missing, with blockers and a launch-day watch list. 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": "review_launch_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoThe feature, what was tested, and the launch plan

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.9/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 the safety profile is carried. The description adds real substance beyond that: the three-valued verdict per area (ready / at risk / missing), that blockers and a launch-day watch list are produced, and the notable directive that it 'returns instructions to follow with the user's text' rather than raw output to relay. It stops short of saying what happens when no plan is supplied.

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-loaded with the verdict type, then the checklist areas, then the outputs. Nearly every clause earns its place; the trailing note about following instructions is slightly tucked away rather than foregrounded.

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 an output schema present, the description need not detail return values, and it still sketches them adequately; one parameter at full coverage means little else is required. The gaps are the unstated empty-plan behavior and the absence of routing guidance against the several adjacent review/plan siblings.

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?

There is a single parameter at 100% schema description coverage, so the schema already explains 'plan'. The description's dimension list implies what the plan ought to cover, adding marginal guidance, but it offers no length, format, or emptiness expectations. Baseline 3 is correct when the schema does the heavy lifting.

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?

Names a specific verb (go/no-go review) and resource (an AI feature's launch plan), then enumerates the nine dimensions checked (evals, grounding, attacks, approvals, cost, latency, monitoring, rollout, support). This clearly separates it from plan_ai_launch (which creates a plan), review_ai_spec and review_ai_incident without needing the schema.

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 context of use is implied — you bring an existing launch plan and get a readiness verdict — but the description never says when to pick this over plan_ai_launch, review_ai_spec, or review_ai_incident, nor any prerequisites. Usage is inferable from the content, not stated.

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