Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Delimit Deploy Plan

delimit_deploy_plan

Generate a deploy plan with built-in security preflight and governance checks, halting on critical findings before any artifact is produced. Use as the first step before building or shipping code.

Instructions

Generate a deploy plan with security preflight (Pro).

When to use: as the first step in the deploy chain. The plan enumerates build steps and bakes in a security audit + governance evaluation before any artifact is produced. When NOT to use: to actually build images (use delimit_deploy_build) or to ship code (use delimit_deploy_publish).

Sibling contrast: this is the planning gate; delimit_deploy_build and delimit_deploy_publish are the execution steps that follow.

Side effects: auto-chains delimit_security_audit (fail-closed on critical findings), then delimit_gov_evaluate, then the underlying deploy_plan handler. Halts and returns status="blocked" on any critical security finding without producing a plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoApplication identity (not a filesystem path). Required.
envNoTarget environment, typically "staging" or "production".
git_refNoGit ref (branch/tag/SHA). Optional; defaults to HEAD.
ventureNoOptional ledger venture identity; repository context remains authoritative.
repo_pathNoExplicit Git worktree root used for health, security, governance, evidence, and attribution.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv4.13.2
    • changedInput schema / properties / app / description
      Previous value: -"Application name (project key in the deploy backend). Required."New value: +"Application identity (not a filesystem path). Required."
    • changedInput schema / properties / git_ref / description
      Previous value: -"Git ref (branch/tag/SHA). Optional; defaults to the backend's notion of HEAD when omitted."New value: +"Git ref (branch/tag/SHA). Optional; defaults to HEAD."
    • addedInput schema / properties / repo_path
      Added value: +{
+  "default": "",
+  "description": "Explicit Git worktree root used for health, security, governance, evidence, and attribution.",
+  "type": "string"
+}
    • addedInput schema / properties / venture
      Added value: +{
+  "default": "",
+  "description": "Optional ledger venture identity; repository context remains authoritative.",
+  "type": "string"
+}
  2. Changed3 schema fields changedv4.7.9
    • addedInput schema / properties / app / description
      Added value: +"Application name (project key in the deploy backend). Required."
    • addedInput schema / properties / env / description
      Added value: +"Target environment, typically \"staging\" or \"production\"."
    • addedInput schema / properties / git_ref / description
      Added value: +"Git ref (branch/tag/SHA). Optional; defaults to the backend's notion of HEAD when omitted."
  3. Changed3 schema fields changedv4.5.5
    • addedInput schema / properties / app / default
      Added value: +""
    • addedInput schema / properties / env / default
      Added value: +""
    • removedInput schema / required
      Removed value: -[
-  "app",
-  "env"
-]
  4. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses side effects in detail: it auto-chains delimit_security_audit and delimit_gov_evaluate before the underlying deploy_plan handler, halts on critical findings, and returns status="blocked" without producing a plan. This is substantial behavioral context that the annotations do not provide.

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 organized into clear labeled sections: purpose, when to use, when not to use, sibling contrast, and side effects. Every section adds distinct value, and the key purpose is front-loaded before any secondary details.

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?

The description covers the tool's role in the deploy chain, exclusions, side effects, and failure behavior. An output schema exists, so return-value documentation is not required here. The only minor gap is that it doesn't explain what happens if the tool is invoked without Pro access or how auth is handled, but this is not essential for correct invocation.

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%, so the schema already documents all five parameters. The description does not add parameter-level meaning, but it doesn't need to because the schema handles it. This matches the baseline for high schema coverage.

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 opens with a specific verb and resource: 'Generate a deploy plan with security preflight.' It clearly distinguishes itself from delimit_deploy_build and delimit_deploy_publish by framing itself as the planning gate, so an agent can immediately tell what this tool does relative to its siblings.

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

Usage Guidelines5/5

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

The description gives explicit 'When to use' and 'When NOT to use' guidance, names the exact alternative tools, and explains the positioning in the deploy chain. This removes ambiguity about when the agent should select this tool versus the build or publish steps.

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/delimit-ai/delimit-mcp-server'

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