Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitlab-getGitlabRepositories

Read-onlyIdempotent

Fetches the list of repositories from a specified GitLab integration, giving you the projects available for deployment in Dokploy.

Instructions

GET /gitlab.getGitlabRepositories

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": {
      "gitlabId": "<gitlabId>"
    },
    "name": "gitlab-getGitlabRepositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
gitlabIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/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 by structured data. The description adds nothing beyond that: no statement about what is returned, whether results are paginated, or whether it performs a live remote call. No contradiction with annotations, but zero added value.

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 short here reflects under-specification rather than conciseness. The text is a bare endpoint path with no front-loaded purpose statement, so there is nothing meaningful to be concise about.

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

Completeness2/5

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

For a one-parameter list tool with no output schema, the description should at minimum say what is listed and what gitlabId identifies. Neither is present, leaving the agent to guess the semantics of the single required argument and the shape of the result.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter gitlabId, and the description does not compensate at all. It never explains that gitlabId is a configured GitLab provider/connection identifier, which is the key ambiguity an agent would face when invoking this tool.

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 raw route string "GET /gitlab.getGitlabRepositories", which essentially restates the tool name. It implies fetching repositories for a GitLab entity, but gives no verb-level framing, no scope, and no differentiation from siblings such as github-getGithubRepositories or gitlab-getGitlabBranches beyond the name itself.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. An agent must infer everything from the tool name, and the description offers no signal about whether this lists all repositories or repositories for a specific GitLab connection.

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