Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-disconnectGitProvider

Idempotent

Disconnect the linked Git provider from a Dokploy compose service by passing its composeId.

Instructions

POST /compose.disconnectGitProvider

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": {
      "composeId": "<composeId>"
    },
    "name": "compose-disconnectGitProvider"
  }
}

Input Schema

NameRequiredDescriptionDefault
composeIdYes

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 already declare idempotentHint=true and openWorldHint=true, so the description's only job is to add context such as what state is destroyed, whether the Git provider credential is deleted or merely unlinked, and required authorization. It supplies none of that, offering only the route string.

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 short and contains no filler, but it is under-specified rather than concise: a single endpoint path that conveys no meaning to an agent unfamiliar with the internal API routing conventions.

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?

This is a mutating operation with one undocumented parameter, no output schema, and no annotations covering its effects, so the description carries the full burden and delivers nothing. An agent cannot determine what happens on success, what is removed, or how to recover.

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 the single required parameter composeId, and the description does not compensate by explaining what identifier is expected or how to obtain it. Nothing in the text clarifies the parameter beyond its name in the schema.

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 HTTP route "POST /compose.disconnectGitProvider", which restates the tool name rather than explaining what disconnecting a Git provider actually does for a compose resource. An agent can guess it removes a Git provider association from a compose project, but the description itself adds no explanatory content beyond the identifier.

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 guidance on when to use this tool, no prerequisites, and no mention of how it differs from the sibling application-disconnectGitProvider or the related gitProvider-remove. The agent must infer everything 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