Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitlab-update

Idempotent

Updates an existing GitLab git provider in Dokploy by changing its name, URLs, application ID, redirect URI, or secret.

Instructions

POST /gitlab.update

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

Input Schema

NameRequiredDescriptionDefault
nameYes
secretNo
gitlabIdYes
gitlabUrlYes
groupNameNo
redirectUriNo
applicationIdNo
gitProviderIdYes
gitlabInternalUrlNo

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?

The annotations carry openWorldHint=true and idempotentHint=true, so the safety/idempotency profile is already supplied by structured data. The description adds nothing beyond the HTTP method: it does not say which fields are replaced versus left untouched, whether secret must be re-supplied, or what happens to omitted optional parameters on a partial update — a real gap for a mutation tool with nine parameters.

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 single line is certainly short, but brevity here is under-specification rather than conciseness — it is a route annotation, not a usable definition. There is nothing to front-load because no content exists.

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, four-required mutation endpoint with no output schema and no annotation covering field semantics, the description supplies none of the information an agent needs. It is far short of what this tool's complexity demands.

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 (name, secret, gitlabId, gitlabUrl, groupName, redirectUri, applicationId, gitProviderId, gitlabInternalUrl), and the description provides no parameter meaning whatsoever. The agent cannot tell from either source how secret differs from applicationId, or what gitlabInternalUrl is for, so the description fails to compensate for the coverage gap.

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 "POST /gitlab.update", which restates the tool name and adds an HTTP verb. It conveys that a GitLab-related record is modified but never says what entity (provider/integration) or which fields are changed, so an agent cannot distinguish it meaningfully from gitlab-create or application-saveGitlabProvider beyond guessing from the name.

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 prerequisite conditions (e.g. must the GitLab provider already exist?), and no mention of any alternative tool. The agent must infer entirely from the name that this edits an existing GitLab configuration rather than creating or testing one.

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