Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-disconnectGitProvider

Idempotent

Disconnect an application from its Git provider using the application ID to stop automated Git-based deployments and remove the linked repository connection.

Instructions

POST /application.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": {
      "applicationId": "<applicationId>"
    },
    "name": "application-disconnectGitProvider"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare openWorldHint=true and idempotentHint=true, but the description adds nothing beyond the HTTP verb. It does not say what is destroyed or detached by disconnecting, whether credentials or webhooks are removed, whether it can be undone, or what authorization is required.

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 reflects under-specification rather than efficiency: a bare route string with no front-loaded statement of purpose or consequence.

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, open-world operation with no output schema, 0% parameter documentation, and annotations that omit destructive and read-only hints. The description supplies none of the missing context an agent needs to call it safely.

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, applicationId, and the description does not compensate by explaining what it identifies or what form it takes. The route name only faintly implies it is the application, leaving the schema to carry the whole burden.

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 an HTTP route, 'POST /application.disconnectGitProvider', which restates the tool name rather than explaining the operation. It conveys no scope, no effect on the application's git integration, and no differentiation from siblings such as 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 Guidelines1/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 when the compose-level or saveGitProvider alternatives would be preferred. An agent has to infer everything from the name.

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