Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitlab-testConnection

Idempotent

Tests connectivity to a configured GitLab instance in Dokploy, verifying the connection and credentials before you use it for deployments or repository operations.

Instructions

POST /gitlab.testConnection

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-testConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
gitlabIdYes
groupNameNo

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 declare openWorldHint=true and idempotentHint=true, so the agent knows this makes an external call and is safe to repeat. The description adds nothing beyond the bare HTTP route — it does not say the call reaches the GitLab API, what a failure looks like, or whether it has side effects on stored provider state. With no readOnly/destructive hints supplied, this leaves real behavioral gaps.

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 brevity here comes from under-specification rather than efficiency — a single route string that conveys no actionable information. There is no front-loaded explanation of purpose or outcome.

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 two-parameter tool with zero schema documentation, no output schema, and only partial annotations, the description should carry the burden of explaining the parameters and the expected result. It does none of that, leaving the agent unable to call it confidently.

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% for both parameters, and the description supplies no meaning for gitlabId or groupName. The agent cannot tell whether gitlabId is a provider record ID or a GitLab instance identifier, nor what role the optional groupName plays in the test.

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.testConnection" — it restates the tool name and HTTP verb without describing what the operation actually does. An agent can infer 'test a GitLab connection' from the name alone, but the description contributes nothing to distinguish it from the many sibling testConnection tools (github, gitea, bitbucket, etc.).

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 or when-not-to-use guidance. Nothing says this validates credentials for a saved GitLab provider versus, say, creating one, nor what prerequisites (existing gitlabId, permissions) are needed before calling it.

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