Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitea-update

Idempotent

Updates an existing Gitea provider connection in Dokploy by changing its URL, credentials, scopes, or tokens so deployments use the correct repository settings.

Instructions

POST /gitea.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": {
      "giteaId": "<giteaId>",
      "giteaUrl": "<giteaUrl>",
      "gitProviderId": "<gitProviderId>",
      "name": "<name>"
    },
    "name": "gitea-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
scopesNo
giteaIdYes
clientIdNo
giteaUrlYes
expiresAtNo
accessTokenNo
redirectUriNo
clientSecretNo
refreshTokenNo
gitProviderIdYes
giteaUsernameNo
giteaInternalUrlNo
organizationNameNo
lastAuthenticatedAtNo

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 supply openWorldHint and idempotentHint, but the description adds nothing beyond them. For a tool that accepts accessToken, clientSecret and refreshToken, it says nothing about permissions, whether fields are replaced or merged, or what happens to omitted credentials.

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 shortness is under-specification rather than conciseness: a bare method-and-path string that front-loads nothing useful about the operation.

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 15-parameter mutation tool with secrets, no output schema and no parameter documentation is left almost entirely unexplained. An agent could not reliably construct a correct call from this definition alone.

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 15 parameters, so the description must carry the burden and it carries none. There is no explanation of whether giteaId/gitProviderId identify the record, how scopes or expiresAt are interpreted, or which fields are optional versus cleared.

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 "POST /gitea.update", which restates the tool name plus an HTTP method. It conveys that something Gitea-related is updated, but not which resource (provider credentials? config?), and it gives no way to distinguish it from gitea-create or the many other *-update siblings.

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 preconditions, and no mention of alternatives such as gitea-create or application-saveGiteaProvider. The agent must guess entirely from the sibling names.

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