Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitea-create

Create a Gitea git provider connection in Dokploy by supplying the server URL, credentials, and organization details for deployment workflows.

Instructions

POST /gitea.create

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": {
      "giteaUrl": "<giteaUrl>",
      "name": "<name>"
    },
    "name": "gitea-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
scopesNo
giteaIdNo
clientIdNo
giteaUrlYes
expiresAtNo
accessTokenNo
redirectUriNo
clientSecretNo
refreshTokenNo
gitProviderIdNo
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 only openWorldHint=true and a title, so the description carries the full burden and delivers nothing. It does not reveal that this is a mutating create with credential fields (accessToken, clientSecret, refreshToken), what gets persisted, or whether re-invocation is idempotent.

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 brief, but the brevity is under-specification rather than economy. A single fragment equal to the tool name carries no front-loaded intent.

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, 2-required mutation tool with zero schema description coverage, no annotations beyond openWorldHint, and no output schema is left entirely undocumented. Nothing an agent needs to call it correctly 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 15 parameters, and the description mentions none of them. Ambiguous pairs like giteaUrl vs giteaInternalUrl, or giteaId vs gitProviderId, receive no explanation anywhere.

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 /gitea.create" does nothing more than restate the tool name and an HTTP method. It never says what resource is being created (a Gitea provider record? a repository?) and gives no basis for distinguishing it from siblings like gitea-update, gitlab-create, or bitbucket-create.

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 any alternative. With gitea-update and gitea-one in the sibling set, an agent has nothing to decide between them from this text.

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