Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitea-getGiteaBranches

Read-onlyIdempotent

Retrieve the branch list for a specified Gitea repository using its owner and repository name, so you can select or verify branches for deployment and infrastructure tasks.

Instructions

GET /gitea.getGiteaBranches

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": {
      "owner": "<owner>",
      "repositoryName": "<repositoryName>"
    },
    "name": "gitea-getGiteaBranches"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYes
giteaIdNo
repositoryNameYes

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 declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no note on pagination, default branch inclusion, auth/provider requirements, or whether it hits a live remote. With annotations carrying the full load and zero descriptive contribution, this is a 1.

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 a single short line with no wasted words, but the brevity comes from under-specification rather than economy. There is no front-loaded statement of purpose beyond an endpoint path.

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 a three-parameter tool with no output schema, no parameter descriptions, and only annotation-level behavioral coverage, the description should explain the resource returned and the role of giteaId. It explains nothing, leaving the agent unable to call it confidently without inspecting the schema.

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 three parameters (owner, repositoryName, giteaId), and the description supplies no meaning for any of them. It does not clarify whether giteaId is optional, whether it selects a configured provider, or how owner/repositoryName are formatted.

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 just the route string 'GET /gitea.getGiteaBranches', which restates the tool name rather than explaining what the tool does. An agent can infer 'fetch branches for a Gitea repo' from the name, but the description itself adds no verb+resource explanation and gives no basis for distinguishing this from github-getGithubBranches, gitlab-getGitlabBranches, or bitbucket-getBitbucketBranches.

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 (e.g. provider must be configured via application-saveGiteaProvider), and no mention of alternatives such as gitea-getGiteaRepositories. The agent must guess entirely from the name.

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