VibeRaven

Get a launch checklist

launch_checklist

Read-onlyIdempotent

launch_checklist({"stack":"nextjs-supabase-vercel"}) Use for a broad pre-launch review of a Lovable + Supabase app or a Next.js + Supabase app on Vercel. For a specific failing request, use search_guides. Returns a published manual checklist with sources and an optional local repo check (npx -y viberaven@1.8.0 check). Limits: checklist guidance only; does not run checks or verify dashboards, code or launch readiness.

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": {
      "stack": "<stack>"
    },
    "name": "launch_checklist"
  }
}

Input Schema

Name	Required	Description	Default
`stack`	Yes	lovable-supabase for a Lovable app with Supabase, nextjs-supabase-vercel for a Next.js app with Supabase deployed on Vercel.

Output Schema

Name	Required	Description	Default
`url`	Yes
`items`	Yes
`stack`	Yes
`title`	Yes
`sources`	Yes
`nextStep`	No
`short_answer`	Yes
`optional_repo_check`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026
- addedOutput schema / properties / nextStep / properties / codingAgentTask
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedOct 31, 2026

addedOutput schema / properties / nextStep

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "label": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "label",
+    "url"
+  ],
+  "type": "object"
+}

First observedOct 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), and the description adds real behavioral detail beyond them: the output is a manually published checklist with sources, and it explicitly disclaims running checks or verifying dashboards, code or launch readiness. It also surfaces the optional local `npx -y viberaven@1.8.0 check` step, which is not derivable from the schema.

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

Conciseness3/5

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

The prose sentences are tight and well front-loaded with purpose and limits, but the leading `launch_checklist({"stack":"nextjs-supabase-vercel"})` snippet is a redundant call example that restates the schema and delays the actual purpose statement.

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 and full schema coverage, the description need not explain return values, and it covers scope, alternative, and limitations well. Minor residual gap: it does not say what to do when the caller is unsure which stack enum applies, though the schema's own descriptions largely cover that.

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 enum parameter is fully documented in the schema, so the description only echoes the two stack names in prose. It adds no format, precedence or default guidance beyond what the enum already provides; baseline 3 applies.

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 verb and resource ('Returns a published manual checklist with sources') and scopes it to two named stacks. It is immediately distinguishable from search_guides, which the description frames as the targeted-failure counterpart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('broad pre-launch review of a Lovable + Supabase app or a Next.js + Supabase app on Vercel') and explicit when-not ('For a specific failing request, use search_guides'), reinforced by a Limits sentence. Nothing about routing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All VibeRaven tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.