webhook-crash-lab-mcp

Overview Schema Source Related Servers Discussions Admin

Run the built-in demo

run_demo

Read-only

Launch the built-in demo credits app in broken or fixed mode to demonstrate common Stripe handler failures, the corrected setup, and what crash-lab checks before real configuration.

Instructions

Run crash-lab against its built-in demo credits app. "broken" shows the typical AI-generated Stripe handler failing; "fixed" shows the same app done right. Needs no config. Use it to show what crash-lab checks before setting up a real config.

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

Input Schema

Name	Required	Description	Default
`mode`	No		broken

Output Schema

Name	Required	Description	Default
`ok`	Yes
`name`	Yes
`summary`	Yes
`failures`	Yes
`nextSteps`	Yes
`notTested`	Yes
`scenarios`	Yes
`reportPath`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.4Nov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior: no configuration is needed and the run is against a bundled sample app, which tells the agent this is a safe, self-contained trial. It does not describe runtime duration or failure modes, but an output schema exists to cover results.

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?

Three short sentences, front-loaded with the action, then the mode meanings, then the usage rationale. No filler or repetition.

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?

For a one-parameter, read-only demo tool with an output schema, the description covers what it runs, what the mode values mean, that no setup is required, and why to use it. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the enum values would otherwise be opaque; the description explains what "broken" and "fixed" actually demonstrate, adding real meaning beyond the raw enum list. It does not mention that mode defaults to "broken", which is the one remaining gap.

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 and resource ("Run crash-lab against its built-in demo credits app") and scopes it as the demo, not the real run. It implicitly separates itself from run_crash_lab by stressing "built-in demo" and "needs no config", though it never names the sibling explicitly.

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

Usage Guidelines4/5

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

Gives clear when-to-use context: show what crash-lab checks before setting up a real config, with no config required. It does not explicitly say when not to use it (e.g., once a real config exists, use run_crash_lab), so the exclusion is left for the agent to infer from the sibling name.

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

Deploy Server