Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitea-testConnection

Idempotent

Tests a Gitea connection for a specified organization to verify credentials and connectivity before configuring deployments or integrations.

Instructions

POST /gitea.testConnection

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gitea-testConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
giteaIdNo
organizationNameNo

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 already supply openWorldHint=true and idempotentHint=true, but the description adds nothing beyond them: no indication of what credentials or network calls are involved, whether failure throws or returns a status, or what state the test touches. The full behavioral burden is left unaddressed.

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 the brevity is under-specification rather than efficiency; a single route string earns little and front-loads no useful information.

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 connectivity-test tool with two parameters, no output schema, and no annotations about safety needs the description to explain inputs and outcome. None of that is present, so the definition is not sufficient to invoke the tool 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?

Schema description coverage is 0% for giteaId and organizationName, and the description supplies no meaning for either. With two undocumented parameters, the description must compensate and does not.

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 raw route string 'POST /gitea.testConnection', which restates the tool name plus an HTTP method. It never says what is being tested or what a successful test means, so an agent must infer purpose purely from the name.

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 guidance on when to call this versus gitea-create, gitea-one, or the other *-testConnection siblings, and no mention of prerequisites such as an existing provider record. The HTTP verb is the only hint at usage.

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