Skip to main content
Glama
chntif
by chntif

workflow_requirement_to_issue

Create a GitLab issue from user requirements, halting further workflow automation.

Instructions

Use when requirement text should only create a GitLab issue and stop there. Do not combine this with workflow_requirement_to_delivery for the same user request. If the issue is already created, continue with workflow_issue_to_delivery instead of calling this tool again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requirement_textYesRaw user requirement text.
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 issue summary.
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 for issue template variables. 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_idNoOptional code project ID used in issue template variables. 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 for template/render context. 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 label 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_labelsNoWhen true, create missing labels in issue project automatically.
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_missingNoWhen true, assign issue to current token user if no assignee is provided.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool call succeeded.
toolYesTool name.
dataNoAnalyze requirement and create issue workflow result.
error_typeNoError type when ok=false.
messageNoError message when ok=false.
Behavior2/5

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

No annotations provided; description lacks behavioral details like destructive actions, authentication, or failure modes. Only usage guidance is given.

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?

Extremely concise (3 sentences) with clear, actionable information; no redundancy.

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?

With output schema present and detailed input schema, the description provides sufficient usage context; however, it omits behavioral details.

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% so baseline 3; description adds no extra parameter meaning beyond schema.

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 creates a GitLab issue from requirement text and stops, distinguishing it from sibling workflow_requirement_to_delivery.

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, when-not-to-combine, and what to do if issue already exists (use workflow_issue_to_delivery).

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