Skip to main content
Glama

bootstrap_validation_loop

Guides interactive deployment validation workflow: detects target platform, verifies environment connectivity, and iteratively executes commands with human approval for secure CI/CD deployment and teardown.

Instructions

GUIDED EXECUTION MODE: This tool guides you through an interactive, step-by-step deployment validation workflow. It does NOT execute commands internally - instead, it tells YOU what commands to run and processes the results iteratively. Workflow: (1) First call with iteration=0: Detects platform (OpenShift/K8s/Docker), validates environment connection, and requests human approval for target platform. (2) Subsequent calls: After running each command and reporting back with output, the tool provides next steps. Environment Validation: Before deployment, the tool verifies connection to the target platform (e.g., oc status for OpenShift, kubectl cluster-info for K8s) and requires explicit human confirmation. Validated Patterns Integration: Automatically identifies base code repositories (e.g., validatedpatterns/common for OpenShift) and guides you to merge them into your project. Deployment Cleanup: Supports CI/CD-style workflows with deployment teardown/restart guidance. Call this tool iteratively, passing previous command output back each time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathNoPath to the project directory.
adrDirectoryNoDirectory where ADRs are storeddocs/adrs
targetEnvironmentNoTarget deployment environmentdevelopment
maxIterationsNoMaximum validation/fix iterations
autoFixNoWhether to generate auto-fix suggestions in guidance
updateAdrsWithLearningsNoUpdate ADRs with deployment learnings (non-sensitive)
currentIterationNoCurrent iteration number (0 for initial call, then increment). Used to track workflow progress.
previousExecutionOutputNoOutput from the previous command execution. Paste the stdout/stderr from running the command that was recommended in the previous iteration.
previousExecutionSuccessNoWhether the previous command execution succeeded (exit code 0). Set to true if command succeeded, false if it failed.
deploymentCleanupRequestedNoSet to true to request deployment cleanup/teardown guidance (for CI/CD workflows that need to delete and restart deployments).
conversationContextNoRich context from the calling LLM about user goals and discussion history
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: it is a guided mode, requires human confirmation, validates environment, checks connections, supports cleanup, and processes previous outputs. It is thorough and leaves no ambiguity about its operation.

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?

The description is well-structured with bold headings, bullet points, and numbered steps. It is front-loaded with the key concept of 'GUIDED EXECUTION MODE'. Every sentence adds value, and it balances detail with clarity without being overly verbose.

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

Completeness5/5

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

Given the tool's complexity (11 parameters, iterative workflow, nested objects), the description is remarkably complete. It covers the initial call, feedback loop, environment validation, patterns integration, cleanup, and provides clear instructions on how to use it. No output schema is present, but the return behavior (next steps) is clearly described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage with descriptions for all parameters. The description adds value by explaining the overall workflow and how parameters like 'currentIteration' and 'previousExecutionOutput' fit into the iterative process. It does not repeat every parameter detail but provides essential context that enhances understanding.

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 tool's purpose as an interactive, step-by-step deployment validation workflow. It specifies that it does not execute commands internally but guides the user. This distinguishes it from sibling tools like 'troubleshoot_guided_workflow' or 'generate_deployment_guidance' that may have different execution models.

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 description explicitly explains the iterative calling pattern ('Call this tool iteratively') and provides a workflow breakdown with initial and subsequent calls. It also mentions that human approval is required and that the tool does not execute commands. However, it does not explicitly state when not to use this tool or compare it directly with siblings.

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/tosin2013/mcp-adr-analysis-server'

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