Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitea-one

Read-onlyIdempotent

Retrieve details for a specific Gitea integration by ID so you can inspect or manage its Dokploy repository connection.

Instructions

GET /gitea.one

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-one"
  }
}

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 indication of what is returned, whether the ID must exist, or what errors look like for an open-world lookup.

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 certainly short, but this is under-specification rather than concision — a bare route string with no front-loaded statement of purpose or outcome. Nothing in the single fragment earns its place as guidance.

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 an undocumented required ID parameter, no output schema, and no explanation of what is retrieved, the definition is not sufficient for an agent to call the tool confidently or correctly.

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?

The single required parameter giteaId has 0% schema description coverage, and the description says nothing about it. The only hint is the parameter name itself, which is entirely from the schema, so the description fails to compensate for the coverage gap.

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 "GET /gitea.one" — it restates the endpoint rather than stating what resource is fetched. An agent learns it is a read of something gitea-related, but cannot tell what object or scope, and cannot distinguish it from siblings like gitea-getGiteaRepositories 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 when-to-use guidance, no preconditions, and no mention of alternatives. The verb "GET" weakly implies retrieval, but nothing tells an agent when this tool is the right choice versus the many sibling gitea-* read tools.

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