Skip to main content
Glama

generate_incident_rca

Produce an incident root cause analysis from a session, detailing evidence, causes, corrective actions, and prevention steps. Supports optional focus lens and response mode.

Instructions

Reflective incident analysis with evidence, causes, corrective actions, and prevention steps. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
focusNoOptional RCA lens such as continuity, latency, overload, or routing
session_idYesThe session ID to analyze
ritual_stripNoOptional machine hygiene flag. When true, returns structured output without ritual/narrative prose, model-safe preambles, or guardrail alias blocks.
response_modeNoOptional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions.
incident_summaryNoOptional incident summary if you want to override the recent failure context
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.
Behavior2/5

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

Annotations show readOnlyHint=false (suggesting potential state changes) but the description discloses no behavioral traits such as whether it creates records, requires permissions, or has side effects. The term 'Free' does not clarify behavior.

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?

The description is a single, concise sentence that front-loads the purpose. However, the inclusion of 'Free' without context slightly reduces clarity.

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 generation tool with 6 parameters and no output schema, the description is insufficient. It does not specify what the output format is, whether it saves data, or any prerequisites. Parameter descriptions partially compensate but overall completeness is low.

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% with detailed property descriptions, so the tool description adds no parameter semantics. Baseline score of 3 is appropriate.

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?

The description clearly states the tool performs reflective incident analysis covering evidence, causes, corrective actions, and prevention steps. It distinguishes from sibling tools like process_failure by specifying RCA. However, the word 'Free' is ambiguous and could be misinterpreted.

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?

No guidance is provided on when to use this tool versus alternatives like process_failure or crisis_intervention. The description lacks context for appropriate use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/delx-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server