Skip to main content
Glama
Sign In
Delx MCP Server

Delx MCP Server

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

process_failure

Process and analyze failures and setbacks, including infra incidents and protocol issues, to identify root causes and improve system resilience.

Instructions

Work through a recent failure or setback, including infra incidents and qualitative protocol failures. Free.

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": {
      "session_id": "<session_id>",
      "failure_type": "<failure_type>"
    },
    "name": "process_failure"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoOptional: What happened?
session_idYesYour active session ID
failure_typeYesType of failure
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.
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

C2.8/5.0
Behavior2/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description only adds the word 'Free.' and the phrase 'Work through a recent failure or setback.' It does not explain what 'work through' entails (e.g., recording, analysis, next actions), nor does it disclose any side effects, state changes, or resource usage. With no behavioral detail, the description fails to add value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence plus 'Free.'), which is concise but under-specified. It lacks structure (e.g., no separation of purpose, usage, or behavior). While brevity is valued, the description sacrifices completeness, making it less helpful for an agent.

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?

With 6 parameters, no output schema, and a complex domain (failure processing), the description is insufficient. It does not explain what the tool returns, how it processes failures, or what side effects occur. Given the richness of sibling tools and the need for clear context, this description is notably incomplete.

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%, and the schema already provides clear descriptions for all parameters (e.g., failure_type enum, context, session_id, ritual_strip, response_mode, response_profile). The description adds no additional meaning or usage context for these parameters, so it meets the baseline but does not exceed it.

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 that the tool works through recent failures or setbacks, including infra incidents and qualitative protocol failures. This provides a specific verb and resource. However, it does not distinguish itself from sibling tools like financial_setback_processing or crisis_intervention, which may lead to ambiguity about when to use this general tool vs. more specific ones.

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?

The description offers no guidance on when to use this tool versus alternatives. It does not mention prerequisites, restrictions, or scenarios where another sibling tool would be more appropriate. This leaves the agent without clear decision support.

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

Deploy Server

Other Tools