webhook-crash-lab-mcp

by Krrishkumar125

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Explain a crash-lab report

explain_report

Read-only

Reads a JSON webhook crash report from CI and returns failures in fix order with why and fix hints plus next steps.

Instructions

Read a JSON report produced by webhook-crash-lab run --json <file> (e.g. from CI) and return the failures in fix order, with why/fix hints and next steps.

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

Input Schema

Name	Required	Description
`cwd`	No
`report`	No	Report JSON, as text or object
`reportPath`	No

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

A3.6/5.0

Behavior3/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 one genuine behavioral trait beyond that: output is ordered in 'fix order' with why/fix hints and next steps, but says nothing about behavior on malformed or missing input, or how the source is resolved.

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?

A single well-formed sentence with the purpose and result front-loaded and no redundant wording. Nothing in it is filler.

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

Completeness3/5

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

The output schema covers return values, so the description needn't detail them. But for a three-parameter tool with two overlapping input paths and zero required parameters, the description leaves a meaningful ambiguity unresolved, which is a real gap for correct invocation.

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

Parameters2/5

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

Schema description coverage is only 33% — only `report` is annotated in the schema, and neither `cwd` nor `reportPath` is mentioned in the description. Critically, the description never clarifies that `report` and `reportPath` are alternative ways to supply the same input, leaving the agent to guess which to populate.

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 (read a JSON report) plus the exact producer command (`webhook-crash-lab run --json <file>`) and what it returns (failures in fix order with hints). This clearly separates it from `run_crash_lab` (which produces reports) and `list_scenarios`.

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 phrase 'e.g. from CI' and the reference to a report already produced by `run --json` imply the precondition (a report must exist), which hints that `run_crash_lab` is the tool to call first. However, no explicit when-to-use/when-not-to-use or named alternative is given, so routing must be inferred.

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

Deploy Server