Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitlab-gitlabProviders

Read-onlyIdempotent

Retrieves the GitLab providers configured in Dokploy so you can identify available GitLab integrations for deployment and repository management.

Instructions

GET /gitlab.gitlabProviders

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gitlab-gitlabProviders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/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 description's only job is to add context beyond that. It adds nothing – no statement of what is returned, whether results are paginated, or whether it reaches out to the GitLab instance (openWorld implies it does).

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 technically waste-free, but it is under-specified rather than concise: it spends its only words echoing the route name instead of front-loading a description of the operation.

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?

With no output schema, the description is the only place an agent could learn what this endpoint returns (a list of provider configurations?) and whether it hits remote GitLab APIs. Neither is covered, leaving the definition incomplete for a zero-param listing tool.

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

Parameters4/5

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

The tool takes zero parameters, so the schema requires no explanation and the baseline is a 4. Nothing in the description contradicts or muddies the parameter story.

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 "GET /gitlab.gitlabProviders", which restates the tool name plus an HTTP verb/path. It never says in plain language that it lists configured GitLab providers, so an agent must infer the resource from the name alone.

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?

There is no when-to-use guidance, no note about prerequisites or authentication, and no pointer to related siblings such as bitbucket-bitbucketProviders or github-githubProviders. The only implicit guidance is the GET verb suggesting a read.

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