Skip to main content
Glama
chntif
by chntif

workflow_requirement_to_delivery

Runs the complete GitLab workflow from requirement to delivery: creates issue, branch, commits, merge request, issue comment, local sync, and updates issue log. Requires a preparation key from prior call.

Instructions

Use when requirement text should run the full chain once: create issue, then continue in the same workflow through branch, commit, MR, issue comment, local sync, and issue log. Before composing commit_actions, first call workflow_prepare_delivery_workspace and use its preparation_key here. Do not combine this with workflow_requirement_to_issue or workflow_issue_to_delivery for the same user request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requirement_textYesRaw user requirement text.
preparation_keyYesRequired key returned by workflow_prepare_delivery_workspace. Delivery is rejected if the prepared base branch is no longer current.
delivery_methodNoDelivery implementation mode. Omit this field unless the user explicitly provided a value. When omitted, the current runtime config value is used (WORKFLOW_DELIVERY_METHOD overrides the built-in default when configured). If the runtime config is still unset, the tool returns a missing-parameter error. Do not infer or auto-generate this value.
source_textNoOptional extra background text for the default issue template.
issue_templateNoOptional full issue markdown template. Supported built-in variables include {{summary}}, {{requirement_text}}, {{source_text}}, {{expected_change}}, {{issue_project_id}}, {{code_project_id}}, {{issue_project_path}}, {{code_project_path}}, {{branch_name}}, {{work_type}}, {{label}}.
template_variablesNoOptional custom variables map merged into issue_template rendering.
english_slugNoOptional branch slug.
work_typeNoOptional git/conventional work type override like feat, fix, docs, refactor, hotfix, feature.
summaryNoOptional short summary used for issue and MR title.
issue_project_idNoIssue project ID. Omit this field unless the user explicitly provided a value. When omitted, the current runtime config value is used (WORKFLOW_ISSUE_PROJECT_ID overrides the built-in default when configured). If the runtime config is still unset, the tool returns a missing-parameter error. Do not infer or auto-generate this value.
issue_project_pathNoIssue project path. Omit this field unless the user explicitly provided a value. When omitted, the current runtime config value is used (WORKFLOW_ISSUE_PROJECT_PATH overrides the built-in default when configured). If the runtime config is still unset, the tool returns a missing-parameter error. Do not infer or auto-generate this value.
code_project_idNoCode project ID. Omit this field unless the user explicitly provided a value. When omitted, the current runtime config value is used (WORKFLOW_CODE_PROJECT_ID overrides the built-in default when configured). If the runtime config is still unset, the tool returns a missing-parameter error. Do not infer or auto-generate this value.
code_project_pathNoCode project path. Omit this field unless the user explicitly provided a value. When omitted, the current runtime config value is used (WORKFLOW_CODE_PROJECT_PATH overrides the built-in default when configured). If the runtime config is still unset, the tool returns a missing-parameter error. Do not infer or auto-generate this value.
labelsNoIssue labels list.
labelNoIssue title prefix and fallback issue label. Omit this field unless the user explicitly provided a value. When omitted, the current runtime config value is used (WORKFLOW_LABEL overrides the built-in default when configured). If the runtime config is still unset, the tool returns a missing-parameter error. Do not infer or auto-generate this value.
auto_create_labelsNoWhether to auto-create missing labels.
assignee_usernameNoSingle assignee username. Omit this field unless the user explicitly provided a value. When omitted, the current runtime config value is used (WORKFLOW_ASSIGNEE_USERNAME overrides the built-in default when configured). If the runtime config is still unset, the tool returns a missing-parameter error. Do not infer or auto-generate this value.
assignee_usernamesNoAssignee usernames list.
assign_to_current_user_if_missingNoWhether to assign issue to current user when no assignee is provided.
target_branchNoMR target branch. Omit this field unless the user explicitly provided a value. When omitted, the current runtime config value is used (WORKFLOW_TARGET_BRANCH overrides the built-in default when configured). If the runtime config is still unset, the tool returns a missing-parameter error. Do not infer or auto-generate this value.
branch_nameNoOptional branch name override.
commit_messageNoOptional commit message.
commit_actionsNoCommit actions list. Required when delivery_method=remote_api.
change_summaryYesChange summary used in MR/log.
test_planYesTest/acceptance plan used in MR description and issue comment.
checkout_local_branchNoWhether to sync and switch local repo to created branch. Omit this field unless the user explicitly provided a value. When omitted, the current runtime config value is used (WORKFLOW_CHECKOUT_LOCAL_BRANCH overrides the built-in default when configured). If the runtime config is still unset, the tool returns a missing-parameter error. Do not infer or auto-generate this value.
issue_comment_bodyNoDirect issue comment body.
implementation_summaryNoImplementation summary for generated issue comment.
acceptance_stepsNoAcceptance steps for generated issue comment.
update_logNoWhether to update local issue log. Omit this field unless the user explicitly provided a value. When omitted, the current runtime config value is used (WORKFLOW_UPDATE_ISSUE_LOG overrides the built-in default when configured). If the runtime config is still unset, the tool returns a missing-parameter error. Do not infer or auto-generate this value.
log_pathNoIssue log path. Omit this field unless the user explicitly provided a value. When omitted, the current runtime config value is used (WORKFLOW_ISSUE_LOG_PATH overrides the built-in default when configured). If the runtime config is still unset, the tool returns a missing-parameter error. Do not infer or auto-generate this value. This field matters only when update_log=true.
log_statusNoIssue log status text.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool call succeeded.
toolYesTool name.
dataNoRequirement to delivery full workflow result.
error_typeNoError type when ok=false.
messageNoError message when ok=false.
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It describes the high-level workflow steps but lacks explicit mention of potential side effects (e.g., creating issues, branches, commits, MRs, modifying repository) or required permissions. It does not mention error conditions or what happens on failure.

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 concise (three sentences) and front-loaded with purpose. It efficiently conveys when to use, prerequisite, and exclusions without extraneous content.

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 the tool's complexity (32 parameters, nested objects, 4 required), the description provides a clear high-level workflow. An output schema exists, so return value details are likely covered there. However, the description could mention expected outcomes (e.g., created MR URL or issue ID) to be more complete.

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% (all parameters have descriptions). The description adds minimal semantic value beyond the schema; it reinforces the prerequisite role of preparation_key but does not enhance understanding of other parameters. Baseline 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 the tool's purpose: to run the full chain from requirement to delivery (create issue, branch, commit, MR, comment, sync, log). It distinguishes from sibling tools like workflow_requirement_to_issue and workflow_issue_to_delivery by specifying the complete workflow.

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 explicitly states when to use this tool (full chain), what prerequisite to fulfill first (call workflow_prepare_delivery_workspace), and which tools not to combine with. This provides clear guidance for agent selection.

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/chntif/mcp-gitlab-workflow'

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