Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitProvider-remove

Destructive

Removes a configured Git provider from Dokploy by its ID, so you can clean up unused source integrations and keep deployment credentials organized.

Instructions

POST /gitProvider.remove

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": {
      "gitProviderId": "<gitProviderId>"
    },
    "name": "gitProvider-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
gitProviderIdYes

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 destructiveHint=true and openWorldHint=true, so the safety profile is partly covered, but the description contributes nothing beyond them: no statement about irreversibility, cascading effects on applications or compose projects bound to the provider, or whether the call is idempotent. For a destructive tool, that silence is a real gap even at the lower annotation-lowered bar.

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 shortness here is under-specification rather than conciseness: the entire text is an endpoint signature with no front-loaded purpose statement or structure. A single sentence naming the resource and the destruction semantics would fit in the same space and actually earn it.

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?

For a destructive, single-parameter mutation with no output schema, an agent needs to know what is destroyed, what depends on it, and where the ID comes from. None of that is present, and the annotations only cover the safety flags.

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?

The single required parameter gitProviderId has 0% schema description coverage, so the description was the only place to explain it and it does not — no hint about where to obtain the ID (for example from gitProvider-getAll) or what form it takes. Baseline 3 is not available here because coverage is far below 50%.

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?

"POST /gitProvider.remove" restates the tool name and HTTP verb rather than describing an action. An agent can guess it deletes a Git provider from the name, but the description itself adds no verb+resource statement and does nothing to distinguish it from siblings such as application-disconnectGitProvider or compose-disconnectGitProvider.

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 prerequisites, and no mention of the disconnect-vs-remove alternatives that the sibling list makes plausible. The route string implies an operation but leaves all routing decisions to inference from the name alone.

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