Skip to main content
Glama

deployment_readiness

Validate deployment readiness by checking test failures, deployment history, and blocking unsafe deployments. Supports multiple environments, strict mode, and emergency bypass with approval.

Instructions

Comprehensive deployment readiness validation with test failure tracking, deployment history analysis, and hard blocking for unsafe deployments. Integrates with smart_git_push for deployment gating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesType of deployment readiness check to perform
projectPathNoPath to project directory (defaults to current working directory)
targetEnvironmentNoTarget deployment environmentproduction
strictModeNoEnable strict validation (recommended for production)
allowMockCodeNoAllow mock code in deployment (NOT RECOMMENDED)
productionCodeThresholdNoMinimum production code quality score (0-100)
mockCodeMaxAllowedNoMaximum mock code indicators allowed
maxTestFailuresNoMaximum test failures allowed (0 = zero tolerance)
requireTestCoverageNoMinimum test coverage percentage required
blockOnFailingTestsNoBlock deployment if tests are failing
testSuiteRequiredNoRequired test suites that must pass
maxRecentFailuresNoMaximum recent deployment failures allowed
deploymentSuccessThresholdNoMinimum deployment success rate required (%)
blockOnRecentFailuresNoBlock if recent deployments failed
rollbackFrequencyThresholdNoMaximum rollback frequency allowed (%)
requireAdrComplianceNoRequire ADR compliance validation
integrateTodoTasksNoAuto-create blocking tasks for issues
updateHealthScoringNoUpdate project health scores
triggerSmartGitPushNoTrigger smart git push validation
emergencyBypassNoEmergency bypass for critical fixes
businessJustificationNoBusiness justification for overrides (required for emergency_override)
approvalRequiredNoRequire approval for overrides
enableMemoryIntegrationNoEnable memory entity storage for deployment assessment tracking and historical analysis
migrateExistingHistoryNoMigrate existing JSON-based deployment history to memory entities
Behavior2/5

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

Description mentions hard blocking and integration, but lacks disclosure of side effects (e.g., updating health scores, creating tasks) or read-only nature. No annotations are present, so the description should compensate more.

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?

Description is two sentences, front-loaded with key purpose, and every sentence adds value. No redundant information.

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?

Given the tool has 24 parameters, no output schema, and no annotations, the description omits important contextual details like return format, behavior when blocking, or side effects, making it incomplete for a tool of this complexity.

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?

Input schema has 100% description coverage for all 24 parameters. The tool description does not add parameter-specific meaning beyond the schema, so baseline 3 is appropriate.

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?

Description clearly states the tool performs comprehensive deployment readiness validation with specific features like test failure tracking and hard blocking. It also mentions integration with smart_git_push, distinguishing it from sibling analysis tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description implies use for validation before deployment by mentioning integration with smart_git_push for gating, but does not explicitly state when to use vs. alternatives or provide exclusions.

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