Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitlab-getGitlabBranches

Read-onlyIdempotent

Fetches the branch list for a specified GitLab repository using owner and repo details, so you can select the right branch for deployment or CI/CD workflows.

Instructions

GET /gitlab.getGitlabBranches

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "owner": "<owner>",
      "repo": "<repo>"
    },
    "name": "gitlab-getGitlabBranches"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
repoYes
ownerYes
gitlabIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: no mention of authentication needs, pagination, result ordering, or what happens with missing repositories, so it contributes no behavioral context of its own.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the brevity is under-specification rather than conciseness; the single fragment conveys no actionable information. Nothing is front-loaded because there is nothing substantive to front-load.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with four undocumented parameters, required auth context, and no output schema, the description is completely inadequate. It offers no return-shape hints, no filtering or limit behavior, and no authentication prerequisite, so an agent cannot call it correctly without trial and error.

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

Parameters1/5

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

Schema description coverage is 0% across four parameters (id, repo, owner, gitlabId), and two of them are required. The description supplies no meaning for any of them, leaving the agent to guess whether 'owner' is a username, namespace, or numeric ID, and how 'id' differs from 'gitlabId'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is only the HTTP verb and endpoint path, 'GET /gitlab.getGitlabBranches', which restates the tool name rather than defining the operation in plain language. The word 'Branches' hints at the resource, but it never says it lists branches for a repository, and it gives no basis for distinguishing it from sibling tools like github-getGithubBranches or gitlab-getGitlabRepositories.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, when not to, or which sibling to pick instead. An agent must infer usage entirely from the tool name.

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