Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-saveGitlabProvider

Idempotent

Saves GitLab provider details for an application in Dokploy, including repository, branch, owner, project ID, and build path, to connect the app to GitLab.

Instructions

POST /application.saveGitlabProvider

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": {
      "applicationId": "<applicationId>",
      "gitlabBuildPath": "<gitlabBuildPath>",
      "gitlabOwner": "<gitlabOwner>",
      "gitlabRepository": "<gitlabRepository>",
      "gitlabId": "<gitlabId>",
      "gitlabProjectId": "<gitlabProjectId>",
      "gitlabPathNamespace": "<gitlabPathNamespace>",
      "gitlabBranch": "<gitlabBranch>"
    },
    "name": "application-saveGitlabProvider"
  }
}

Input Schema

NameRequiredDescriptionDefault
gitlabIdYes
watchPathsNo
gitlabOwnerYes
gitlabBranchYes
applicationIdYes
gitlabBuildPathYes
gitlabProjectIdYes
enableSubmodulesNo
gitlabRepositoryYes
gitlabPathNamespaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations supply only openWorldHint=true and idempotentHint=true, leaving destructive/read-only semantics, permission requirements, and whether an existing provider config is overwritten entirely undisclosed. The description contributes no behavioral context whatsoever, so it fails to carry the remaining burden for a mutation tool.

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 only because it is under-specified: a bare endpoint path with no front-loaded statement of purpose, scope, or effect. Brevity here is a deficiency rather than efficiency.

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 10-parameter write tool with no output schema and sparse annotations, the definition provides essentially nothing an agent needs to invoke it correctly. All critical information about required inputs and side effects is missing.

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 10 parameters, including 8 required fields like gitlabProjectId, gitlabPathNamespace, and gitlabBuildPath whose meaning and format are entirely undocumented. The description adds no parameter meaning, so nothing compensates for the schema 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 the route string "POST /application.saveGitlabProvider", which essentially restates the tool name in HTTP form. It implies a write of GitLab provider configuration but never states in prose what the tool actually does or how it differs from siblings such as application-saveGithubProvider or application-saveGitProvider.

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 when to pick this over the many sibling save*Provider tools. An agent must infer selection purely from the 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