Skip to main content
Glama
MCP Dokploy Online
by igoruam

github-update

Idempotent

Updates an existing GitHub integration configuration in Dokploy using its ID, provider ID, and GitHub App name.

Instructions

POST /github.update

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": {
      "githubId": "<githubId>",
      "name": "<name>",
      "gitProviderId": "<gitProviderId>",
      "githubAppName": "<githubAppName>"
    },
    "name": "github-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
githubIdYes
gitProviderIdYes
githubAppNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/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 description only needed to add what mutations destroy, what auth/ownership is required, or how partial vs full replacement behaves. It adds none of that — the route string conveys no behavior beyond the method.

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 is under-specification rather than conciseness: a bare route string with no verb, object, or constraint. Nothing is front-loaded because there is no substance to front-load.

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 mutation tool with four required, entirely undocumented parameters, no output schema, and only two hints in annotations leaves an agent unable to call it correctly. The description does nothing to close that gap.

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?

Four required parameters (githubId, name, gitProviderId, githubAppName) have 0% schema description coverage and the description supplies no meaning for any of them — notably whether githubId identifies the record to update or whether gitProviderId must reference an existing provider.

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 /github.update" only restates the HTTP method and the tool name as a route; it never says what a GitHub 'update' actually changes (provider config, app credentials, name). It is a tautology rather than a stated verb+resource with meaning.

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 alternatives such as application-saveGithubProvider, github-one, or any of the sibling *-update tools. An agent has nothing to route on beyond guessing 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