mcp-gitlab-workflow

workflow_sync_local_branch

Fetch or pull latest changes and checkout a specific local branch to sync your repository.

Instructions

Use when local repository should fetch/pull and switch to a target branch. Local git operations only.

Input Schema

TableJSON Schema

Name	Required	Description
`branch_name`	Yes	Target branch to checkout locally.
`repo_path`	Yes	Local repository path.
`remote_name`	No	Git remote name. Omit this field unless the user explicitly provided a value. When omitted, the current runtime config value is used (WORKFLOW_LOCAL_REMOTE_NAME 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.
`base_branch`	No	Optional base branch to pull before checkout. Omit this field unless the user explicitly provided a value. When omitted, the current runtime config value is used (WORKFLOW_BASE_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.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the tool call succeeded.
`tool`	Yes	Tool name.
`data`	No	Local repository sync and branch checkout result.
`error_type`	No	Error type when ok=false.
`message`	No	Error message when ok=false.

Tool Definition Quality

A4/5.0

Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It states 'Local git operations only' and implies fetch/pull and branch switching, but lacks details on side effects like conflicts, uncommitted changes, or branch creation fallback.

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 a single, efficient sentence that clearly communicates purpose and scope without unnecessary words.

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?

An output schema exists, so return values are covered. The description adequately explains the main action and scope, but could mention prerequisites like repository existence or error scenarios for a more complete picture.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds significant meaning for 'remote_name' and 'base_branch' by advising to omit unless user-provided and explaining runtime config fallback, which is valuable beyond the 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 synchronizes a local repository by fetching/pulling and switching to a target branch. The phrase 'Local git operations only' distinguishes it from sibling tools that operate on remote GitLab resources.

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

Usage Guidelines4/5

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

The description explicitly says 'Use when local repository should fetch/pull and switch to a target branch.' It provides clear context for when to use the tool and implies exclusion for remote operations via 'Local git operations only.'

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

Install Server

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

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