Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-saveGiteaProvider

Idempotent

Saves a Gitea provider configuration to a Dokploy application, linking repository, branch, owner, and build path for deployments.

Instructions

POST /application.saveGiteaProvider

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>",
      "giteaBuildPath": "<giteaBuildPath>",
      "giteaOwner": "<giteaOwner>",
      "giteaRepository": "<giteaRepository>",
      "giteaId": "<giteaId>",
      "giteaBranch": "<giteaBranch>"
    },
    "name": "application-saveGiteaProvider"
  }
}

Input Schema

NameRequiredDescriptionDefault
giteaIdYes
giteaOwnerYes
watchPathsNo
giteaBranchYes
applicationIdYes
giteaBuildPathYes
giteaRepositoryYes
enableSubmodulesNo

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 idempotentHint=true and openWorldHint=true, but the description adds nothing beyond repeating the route. It does not say whether an existing provider is overwritten, what happens to unrelated fields, whether credentials must already exist, or what the call returns.

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 brief but that brevity reflects under-specification rather than efficiency. A bare route string is not front-loaded explanatory content that an agent can act on.

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?

For an 8-parameter mutation tool with no output schema and no field documentation, the description is wholly inadequate. It leaves the agent unable to determine required values, side effects, or how the six required fields relate to one another.

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?

There are 8 parameters (6 required) with 0% schema description coverage, so the description carries the full burden of explaining them. It supplies no meaning for giteaId, giteaOwner, giteaBuildPath, watchPaths, enableSubmodules, or the interaction between them, leaving half the surface undocumented.

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 /application.saveGiteaProvider", which restates the tool name rather than explaining what saving a Gitea provider means. An agent can vaguely infer a write to Gitea provider configuration, but nothing distinguishes this from siblings like application-saveGithubProvider or application-saveGitProvider.

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?

No guidance is given on when to use this versus the many sibling save-provider tools or gitea-update / gitea-create. There are no prerequisites, no exclusions, and no indication of what configuration state is required before calling it.

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