Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitlab-create

Creates and configures a GitLab integration in Dokploy using credentials and URLs, enabling deployments to authenticate and connect to GitLab repositories.

Instructions

POST /gitlab.create

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": {
      "authId": "<authId>",
      "name": "<name>",
      "gitlabUrl": "<gitlabUrl>"
    },
    "name": "gitlab-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
authIdYes
secretNo
gitlabUrlYes
groupNameNo
redirectUriNo
applicationIdNo
gitProviderIdNo
gitlabInternalUrlNo

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?

The only annotation is openWorldHint=true, so the description bears the full burden of behavioral disclosure and supplies none. Beyond the implied write from "POST", there is no mention of required authentication scopes, whether an existing GitLab integration is modified or a new one persisted, error conditions, or side effects.

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?

The text is brief but only because it is under-specified rather than economical; it is a bare method-and-path string with no front-loaded statement of purpose. There is no structure to speak of.

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 nine-parameter mutation tool with no output schema, no parameter descriptions, and minimal annotations, the description should explain at least the created resource and the roles of the required fields. It provides none of this, leaving the agent with almost no information beyond the verb.

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 nine parameters (authId, name, gitlabUrl, secret, groupName, redirectUri, applicationId, gitProviderId, gitlabInternalUrl), and the description explains none of them. Critical ambiguities such as the difference between gitlabUrl and gitlabInternalUrl, or the role of secret versus applicationId, go entirely unaddressed.

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 essentially a restatement of the tool name plus an HTTP method ("POST /gitlab.create"). It conveys that this is a write/create call to a GitLab endpoint but never says what entity is created (a connection, provider, or application), so an agent cannot distinguish it from siblings like application-saveGitlabProvider or gitea-create.

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

Usage Guidelines2/5

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

No when-to-use, when-not-to-use, or prerequisite information is given. Nothing indicates how this differs from gitlab-update, gitlab-testConnection, or the many other *-create tools, leaving the agent to guess from the parameter names alone.

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