Vibe Engineering MCP

project_resume

Generate complete continuation context for a fresh AI worker to resume development on a project, including requirements, architecture, tasks, and checkpoints.

Instructions

Provides complete, high-density continuation context for a fresh worker model resuming development

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": {
      "projectId": "<projectId>"
    },
    "name": "project_resume"
  }
}

Input Schema

Name	Required	Description	Default
`projectId`	Yes	ID of the project to resume

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not state whether the operation is read-only or mutates project state, nor permissions required. 'High-density' hints at output size but no other behavioral traits are disclosed.

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?

Single sentence, front-loaded, no wasted words. Well-structured for the small amount of information provided.

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

Completeness2/5

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

With no annotations and no output schema, the description should disclose the safety/mutation profile and operation. It only states what context is returned, leaving the agent unsure whether resuming changes persisted state or is a pure read. Incomplete for a state-ambiguous operation.

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%, so projectId is fully documented in the schema. The description adds no parameter-level detail, but the baseline of 3 applies when schema does the heavy lifting.

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 the tool provides continuation context for resuming development, naming the resource and scenario. However, 'provides' is a weak verb and it doesn't distinguish from siblings like project_inspect or checkpoint_load. Clear but no sibling differentiation.

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?

Gives an implicit usage scenario ('fresh worker model resuming development') but no explicit when-to-use instruction or alternatives. No mention of project_inspect or checkpoint_load, so an agent cannot tell which sibling to choose.

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