Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitea-getGiteaUrl

Read-onlyIdempotent

Retrieves the Gitea URL for a specified integration ID so you can access the correct repository endpoint in Dokploy.

Instructions

GET /gitea.getGiteaUrl

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>"
    },
    "name": "gitea-getGiteaUrl"
  }
}

Input Schema

NameRequiredDescriptionDefault
giteaIdYes

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 readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered structurally. The description adds nothing beyond that — no statement about what is returned, whether a provider must exist first, or what happens with an unknown giteaId.

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 with no wasted words, but that brevity is under-specification rather than economy — the single line conveys a route, not a capability.

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?

With no output schema, the description needed to state that a URL string is returned; it does not. For a tool whose entire value is a returned value, this leaves the agent unable to predict the result.

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% for the single required parameter giteaId, so the description carries the full burden and provides none. It never explains that giteaId identifies a configured provider or how to obtain one.

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 essentially an HTTP route restatement, 'GET /gitea.getGiteaUrl', which only parrots the tool name. It does not say what value is produced (presumably the base URL of a configured Gitea instance) or how it differs from siblings like gitea-one or gitea-giteaProviders.

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 guidance on when to call this versus gitea-giteaProviders, gitea-one, or gitea-testConnection. The agent must infer the selection criteria entirely from 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