Skip to main content
Glama
tosin2013

mcp-adr-analysis-server

by tosin2013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

troubleshoot_guided_workflow

Read-onlyIdempotent

Analyze structured failure data to generate targeted test plans, with memory tracking and intelligent suggestions for ADRs and research on recurring issues.

Instructions

Structured failure analysis and test plan generation with memory integration for troubleshooting session tracking and intelligent ADR/research suggestion capabilities - provide JSON failure info to get specific test commands

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
failureNoStructured failure information (required for analyze_failure and generate_test_plan)
todoPathNoPath to TODO.md fileTODO.md
operationYesType of troubleshooting operation
projectPathNoPath to project directory (optional)
adrDirectoryNoADR directory pathdocs/adrs
enableAdrSuggestionNoEnable automatic ADR suggestion based on recurring failures
enableMemoryIntegrationNoEnable memory entity storage for troubleshooting session tracking and pattern recognition
enablePatternRecognitionNoEnable automatic pattern recognition and failure classification
enableResearchGenerationNoEnable automatic research question generation for persistent problems

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.7.46
    • removedInput schema / properties / conversationContext
      Removed value: -{
-  "additionalProperties": false,
-  "description": "Rich context from the calling LLM about user goals and discussion history",
-  "properties": {
-    "budget": {
-      "description": "Budget or resource constraints (e.g., \"limited budget\", \"enterprise scale\")",
-      "type": "string"
-    },
-    "constraints": {
-      "description": "Limitations, compliance requirements, or restrictions (e.g., [\"GDPR compliance\", \"budget under $50k\", \"minimal downtime\"])",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "focusAreas": {
-      "description": "Specific areas of concern or interest (e.g., [\"security\", \"performance\", \"maintainability\"])",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "humanRequest": {
-      "description": "Original human request text for context restoration and knowledge graph storage",
-      "type": "string"
-    },
-    "previousContext": {
-      "description": "Relevant context from previous conversation (e.g., \"User mentioned concerns about database splitting\")",
-      "type": "string"
-    },
-    "projectPhase": {
-      "description": "Current project phase (e.g., \"planning\", \"development\", \"migration\", \"production\")",
-      "type": "string"
-    },
-    "requirements": {
-      "description": "Specific requirements or preferences mentioned",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "timeline": {
-      "description": "Timeline or urgency information (e.g., \"launch in 3 months\", \"urgent migration\")",
-      "type": "string"
-    },
-    "userGoals": {
-      "description": "Primary objectives the user wants to achieve (e.g., [\"microservices migration\", \"improve security\"])",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "userRole": {
-      "description": "User's role or expertise level (e.g., \"senior architect\", \"developer\", \"project manager\")",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
  2. Changed4 schema fields changedv1.0.0
    • addedInput schema / properties / enableAdrSuggestion
      Added value: +{
+  "default": true,
+  "description": "Enable automatic ADR suggestion based on recurring failures",
+  "type": "boolean"
+}
    • addedInput schema / properties / enableMemoryIntegration
      Added value: +{
+  "default": true,
+  "description": "Enable memory entity storage for troubleshooting session tracking and pattern recognition",
+  "type": "boolean"
+}
    • addedInput schema / properties / enablePatternRecognition
      Added value: +{
+  "default": true,
+  "description": "Enable automatic pattern recognition and failure classification",
+  "type": "boolean"
+}
    • addedInput schema / properties / enableResearchGeneration
      Added value: +{
+  "default": true,
+  "description": "Enable automatic research question generation for persistent problems",
+  "type": "boolean"
+}
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile with readOnlyHint, idempotentHint, and destructiveHint. The description adds useful behavioral context around memory integration, ADR/research suggestions, and test-command output. However, 'memory integration for troubleshooting session tracking' is ambiguous about whether the tool persists state, which creates some tension with the readOnlyHint; this isn't a direct contradiction but a meaningful gap.

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 sentence with the core purpose front-loaded and the actionable instruction at the end. It includes some mild fluff like 'intelligent' and 'capabilities,' but overall it is reasonably compact and contains no redundant restatement of the tool name.

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?

This is a complex tool with nine parameters, nested objects, three operation modes, and no output schema, yet the description remains high-level. An agent cannot tell what 'full_workflow' does differently from the other operations, what the exact return shape is, or how the memory/ADR/research features manifest in the result. The schema covers parameter structure but not behavioral completeness.

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%, so the description doesn't need to re-document parameters. It does add the useful clue that failure info should be JSON and that the output includes test commands, but it doesn't explain the three operation modes or how optional toggles like memory integration affect behavior. Baseline 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 identifies a specific purpose: structured failure analysis and test plan generation from JSON failure information. It clearly differentiates from many sibling tools by combining troubleshooting with memory integration and ADR/research suggestions, though it uses noun-phrase style rather than an explicit verb and doesn't name an alternative tool.

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?

The phrase 'provide JSON failure info to get specific test commands' gives a clear usage context: this tool is for analyzing a failure and producing test commands. It doesn't state explicit exclusions or when-not-to-use, but the intended scenario is reasonably clear from the description and title.

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