Skip to main content
Glama
devops-deploy-guard-mcp-server

devops-deploy-guard-mcp-server

by awais2o

Diagnose & Apply Mid-Deployment Fix (v1.7.0)

diagnose_and_fix
Destructive

Execute SSH fix commands on paused deployments to resolve mid-deployment issues without altering deployment state or git commit status.

Instructions

Executes a diagnostic fix command via SSH for a paused deployment without breaking deployment state or resetting git commit status.

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": {
      "plan_id": "<plan_id>",
      "fix_command": "<fix_command>"
    },
    "name": "diagnose_and_fix"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesThe plan_id of the paused deployment plan
fix_commandYesThe fix command to execute via SSH to resolve mid-deployment issue

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

A4.2/5.0
Behavior4/5

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

Adds context beyond annotations by specifying SSH execution and state preservation, reassuring despite destructiveHint=true; does not cover failure modes or retry behavior.

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?

Single, front-loaded sentence with no wasted words; efficient and focused.

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

Completeness4/5

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

With 2 required params and no output schema, description is mostly adequate but could include example fix_command or return value hint.

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 baseline 3 applies; description adds no extra meaning to the parameters (e.g., format of fix_command).

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?

The description clearly states the action (executes a diagnostic fix command via SSH), context (paused deployment), and constraints (preserves state and git status), distinguishing it from siblings like rollback_execution.

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?

Explicitly notes when to use ('for a paused deployment') and what it avoids ('without breaking deployment state or resetting git commit status'), but lacks explicit alternatives or when-not-to-use.

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