Skip to main content
Glama

_delimit_release_impl

Dispatches to six release actions (plan, validate, status, rollback, history, sync) for unified multi-service release management.

Instructions

Unified release-management entry point — dispatches to one of six actions.

When to use: as the single MCP-registered release surface (delimit_release) when the caller wants to pick the release operation by name in one call rather than choosing a specific delimit_release_* alias. Release-tier means whole-environment, multi-service versions (the rollup across apps), as opposed to the deploy-tier (per-app SHA) covered by the delimit_deploy_* tools. When NOT to use: from internal code paths — prefer the specific alias (delimit_release_plan, delimit_release_validate, delimit_release_status, delimit_release_rollback, delimit_release_history, delimit_release_sync) for clarity and so each action's docstring and license gate show up at the right call site. For per-app rollout state use delimit_deploy_status; to ship code use delimit_deploy_publish; for OpenAPI spec linting use delimit_lint.

Sibling contrast: each delimit_release_ wrapper is a thin alias over this implementation; they exist so the action's docstring lives at the right name. This is the dispatch core. delimit_release_validate routes through a shared _release_validate chain, and the public delimit_release_sync exposes its sub-action as a param named action, which this function receives as sync_action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoWhich release operation to perform. One of "plan", "validate", "status", "rollback", "history", "sync". Default "status". Other values return a deterministic error.status
environmentNoTarget environment, "staging" or "production". Default "production".production
versionNoRelease version (auto-detected from git tags if empty). Used by "plan", "validate", and "rollback" (as the expected current version to roll back FROM).
repositoryNoRepository path. Default ".". Used only by "plan"..
servicesNoOptional list of service names to scope the plan; None = all services in the repo manifest. Used only by "plan".
to_versionNoPrior release version to roll back to. Required for "rollback"; ignored otherwise.
limitNoMaximum number of releases to return. Default 10. Used only by "history".
sync_actionNoSub-action for "sync" — "audit" (default) or "config". Ignored by other actions.audit

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Despite no annotations, the description discloses its role as a dispatcher, lists the six actions, notes that invalid actions return a deterministic error, and explains the sync_action sub-action. It could be more explicit about potential destructive behaviors (e.g., rollback) or side effects, but it provides sufficient transparency for a dispatch function.

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 well-structured with clear sections (purpose, when to use/not use, sibling contrast) and each sentence adds value. It could be slightly more concise, but it remains efficient and front-loaded.

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?

Given 8 optional parameters, presence of output schema, and a large sibling set, the description adequately explains its role as the dispatch core and its relationship with aliases and other tools. It doesn't cover every detail of each action, but it provides sufficient context 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 coverage is 100% with detailed descriptions for each parameter, including defaults and usage scope per action. The description adds no extra parameter information beyond the schema, so a baseline score of 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?

The description clearly states it is a 'unified release-management entry point' that dispatches to six specific actions. It distinguishes itself from sibling aliases (e.g., delimit_release_plan) and from deploy-tier tools (delimit_deploy_*), making its purpose and scope unambiguous.

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?

Explicitly provides when to use (as the single MCP surface for release operations by name) and when NOT to use (prefer specific aliases in internal code). Also contrasts with related tools like delimit_deploy_status and delimit_lint, offering comprehensive guidance.

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