Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-saveGithubProvider

Idempotent

Saves a GitHub provider configuration for a Dokploy application, linking the repository, owner, branch, build path, and trigger settings needed to deploy from GitHub.

Instructions

POST /application.saveGithubProvider

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>",
      "repository": "<repository>",
      "owner": "<owner>",
      "buildPath": "<buildPath>",
      "githubId": "<githubId>",
      "branch": "<branch>"
    },
    "name": "application-saveGithubProvider"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYes
branchYes
githubIdYes
buildPathYes
repositoryYes
watchPathsNo
triggerTypeNopush
applicationIdYes
enableSubmodulesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/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, so the safety profile is partly covered. The description adds nothing beyond that — no statement of what existing provider configuration is overwritten, whether credentials (githubId) must be pre-registered, or what happens to watchPaths and triggerType defaults on repeated calls. For a mutation of application build settings, that is a real gap.

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 that brevity reflects under-specification rather than economy — the single route string spends no words on meaning. There is no structure to front-load because there is no content.

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?

A 9-parameter mutation endpoint with 6 required fields, an enum, and no output schema needs a substantive description, and this provides only a route. Nothing an agent needs in order to call it correctly — required auth/provider linkage, side effects, or field meaning — is present.

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% across 9 parameters, including 6 required ones, so the description carries the full burden and provides none. It does not explain that buildPath is the repository build context, that githubId links to a stored GitHub connection, or how watchPaths interacts with triggerType's push/tag enum.

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 route string "POST /application.saveGithubProvider", which restates the tool name in HTTP form. It does convey the method is a write (POST) and that it targets an application's GitHub provider, but it never says what saving a GitHub provider actually configures. It does not distinguish this from saveGitProvider, saveGitlabProvider, or saveBitbucketProvider in the sibling list.

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 when to prefer this over the neighboring saveGitProvider or saveGitlabProvider tools. The agent must infer everything about selection 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