Vibe Engineering MCP

integration_verify

Run end-to-end integration harnesses across modules to verify complete system behavior and catch cross-module failures before release.

Instructions

Executes end-to-end integration harness across multiple modules to verify complete system behavior

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": "<name>",
      "description": "<description>",
      "modulesInvolved": "<modulesInvolved>",
      "integrationCommand": "<integrationCommand>"
    },
    "name": "integration_verify"
  }
}

Input Schema

Name	Required	Description
`cwd`	No	Optional working directory
`name`	Yes	Name of the integration test
`projectId`	Yes	ID of the project
`description`	Yes	Description of cross-module interaction being verified
`expectedPattern`	No	Regex pattern expected in output
`modulesInvolved`	Yes	List of module IDs involved
`integrationCommand`	Yes	Command to run integration test suite

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

C2.9/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 behavioral burden. It says the tool 'executes' a command but does not disclose side effects, whether it requires a built workspace, what happens on failure, or whether it is safe to re-run – significant gaps for an execution tool.

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 efficient sentence with the verb and scope front-loaded and no filler. It is appropriately sized, though the terseness leaves the behavioral and usage gaps unaddressed.

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?

For a 7-param execution tool with no annotations and no output schema, the description is too thin. It omits failure behavior, prerequisites (e.g., that modulesInvolved must already exist), and any sense of what a successful versus failed verification yields.

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%, so the seven parameters (projectId, name, modulesInvolved, integrationCommand, expectedPattern, etc.) are already fully documented. The description adds no syntax, format, or constraint detail beyond the schema, so the baseline of 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 specific verb (Executes) and resource (end-to-end integration harness across multiple modules) with a clear outcome (verify complete system behavior). The 'across multiple modules' scope implicitly separates it from single-module siblings like contract_verify or module_run, though no sibling is named.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The 'end-to-end' phrasing hints at its place after modules exist, but the agent must infer when this beats contract_verify or module_run.

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