Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delimit Release Plan

delimit_release_plan
Read-onlyIdempotent

Generate a release plan from git history to enumerate services and changes ahead of a release and surface the version to bump. Scopes by service and environment.

Instructions

Generate a release plan from git history (Pro).

When to use: ahead of cutting a release, to enumerate the services and changes that will ship and surface the version to bump. When NOT to use: to validate readiness (use delimit_release_validate) or to ship code (use delimit_deploy_publish).

Sibling contrast: delimit_deploy_plan plans a deploy of one app; this plans a multi-service release across an environment.

Side effects: read-only on git/repo state; gated by require_premium. Calls backends.tools_infra.release_plan.

Prerequisite: requires Delimit Pro. An unlicensed call returns {"error": ..., "upgrade": "https://delimit.ai/pricing"} without running.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
versionNoRelease version. Auto-detected from git tags if empty.
servicesNoOptional list of service names to scope the plan; None = all services in the repo manifest.
repositoryNoRepository path. Default "." (cwd)..
environmentNoTarget environment, "production" or "staging". Default "production".production

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv4.7.9
    • addedInput schema / properties / environment / description
      Added value: +"Target environment, \"production\" or \"staging\". Default \"production\"."
    • addedInput schema / properties / repository / description
      Added value: +"Repository path. Default \".\" (cwd)."
    • addedInput schema / properties / services / description
      Added value: +"Optional list of service names to scope the plan; None = all services in the repo manifest."
    • addedInput schema / properties / version / description
      Added value: +"Release version. Auto-detected from git tags if empty."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context beyond this: it states the call is read-only on git/repo state, gated by require_premium, invokes backends.tools_infra.release_plan, and returns an upgrade error without running when unlicensed. This is rich, concrete behavioral disclosure.

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 labeled sections, zero filler, and the core purpose front-loaded. Each sentence earns its place: purpose, usage, exclusions, sibling contrast, side effects, backend call, and prerequisite. The formatting makes it easy for an agent to scan.

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 output schema exists, all parameters are documented, and annotations cover safety, the description is fully complete for correct selection and invocation. It covers when to use, when not to use, the sibling distinction, side effects, backend call, and licensing prerequisite. Nothing material is missing.

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 fully documents all four parameters. The description adds context about surfacing the version to bump and multi-service release planning, but it does not need to explain individual parameters. Baseline 3 is appropriate because the schema carries the semantic load.

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 release plan from git history.' It clarifies the output is a multi-service release plan and explicitly contrasts with delimit_deploy_plan, so an agent can distinguish it from a similarly named sibling without inspecting schemas.

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 provides explicit 'When to use' and 'When NOT to use' guidance, naming delimit_release_validate and delimit_deploy_publish as alternatives. It also contrasts with delimit_deploy_plan, making the selection criteria unambiguous.

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

Deploy Server

Other Tools