Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitlab-one

Read-onlyIdempotent

Retrieve details for a specific GitLab instance by its ID, enabling targeted access to GitLab configuration and source-control data through Dokploy.

Instructions

GET /gitlab.one

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

Input Schema

NameRequiredDescriptionDefault
gitlabIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/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 safety profile is covered without the description's help. The description adds nothing beyond that — no mention of what the identifier refers to, whether a missing record errors or returns empty, or what authentication/connection state is required for the open-world call.

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 extremely short, but brevity here reflects under-specification rather than concision — the four-token route string leaves the caller with no actionable information. Nothing is front-loaded because nothing is stated beyond the endpoint.

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 one required parameter, no output schema, and only hint-level annotations, the description carries the burden of explaining the identifier and the retrieval outcome, and it does neither. The annotations salvage a minimal safety picture, but the definition is not sufficient to invoke the tool confidently.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter gitlabId, and the description does not compensate. It never says whether gitlabId is a provider UUID, a name, or a path segment, so the agent has no basis for supplying a valid value.

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?

"GET /gitlab.one" restates the tool name and HTTP verb rather than describing the action in agent terms. An agent can infer it retrieves a single GitLab entry, but nothing distinguishes it from gitlab-gitlabProviders (list) or gitlab-create in the sibling set.

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 mention of alternatives such as the list or create variants, and no stated prerequisites. The agent must guess that this is the single-resource fetch and not the provider-listing call.

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