Skip to main content
Glama

henry_predict_failure_scenarios

Predicts likely failure scenarios for an app and module pair using static findings, returning each scenario's condition, symptom, cause, severity, and confidence to guide validation.

Instructions

Predict likely failure scenarios for an app + module pair.

Each scenario includes title, condition, symptom, cause, evidence, severity, confidence, and validation_needed. Only scenarios supported by static findings are produced.

Args: app_path: Path to the application file. module_path: Path to the module file. limit: Maximum number of scenarios to return (default 1000). offset: Number of scenarios to skip (default 0).

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": {
      "app_path": "<app_path>",
      "module_path": "<module_path>"
    },
    "name": "henry_predict_failure_scenarios"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
app_pathYes
module_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden. It does disclose one genuinely useful trait: output is limited to scenarios backed by static findings, and each scenario carries severity/confidence/validation_needed. It omits cost, latency, auth, and whether prior analysis state is required before calling.

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?

Purpose is front-loaded and the Args block is scannable. The enumerated list of eight return fields (title, condition, symptom, cause, evidence, severity, confidence, validation_needed) is largely redundant given an output schema exists, which costs it a point.

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?

For a 4-parameter tool with no annotations, the definition covers inputs and repeats output shape but leaves gaps: no indication of whether this is expensive, whether it depends on a prior analysis run, or how app_path and module_path relate. Adequate but not complete for an unannotated tool.

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 0%, so the description must compensate, and it does list all four parameters. However, the explanations for app_path and module_path only lightly expand the schema titles ("App Path" → "Path to the application file"), adding little about accepted formats or path conventions; limit/offset semantics are the only substantive additions.

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?

"Predict likely failure scenarios for an app + module pair" gives a specific verb (predict) and resource (failure scenarios) plus the exact scope of inputs. An agent can distinguish it from henry_explain_finding or henry_inspect_file, but the description never names or contrasts those siblings explicitly.

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?

Usage is only implied by the purpose statement; there is no statement of when to reach for this versus henry_analyze_pair or henry_explain_finding, and no prerequisites (e.g. whether an analysis must exist first). The line "Only scenarios supported by static findings are produced" is a behavioral constraint, not selection guidance.

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