Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Get branch

gitea_get_branch
Read-only

Retrieve details for a specific branch, including its latest commit and protection settings, to verify branch state and review repository protection rules.

Instructions

[UNIFIED] Get details of a specific branch including latest commit and protection settings.

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": {
      "site": "<site>",
      "owner": "<owner>",
      "repo": "<repo>",
      "branch": "<branch>"
    },
    "name": "gitea_get_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYes
siteYes
ownerYes
branchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds useful return-content context (latest commit, protection settings) but says nothing about required permissions, error behavior for missing branches, or whether the branch name accepts slashes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the returned fields attached, and no filler or redundancy. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with no output schema, stating what is returned covers a lot, so the description is nearly adequate. The gap is the undocumented parameters, especially "site", and the absence of any failure or permission context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden for all four parameters, but it names none of them. Owner, repo, and branch are inferable from their names, yet "site" is genuinely ambiguous — presumably the Gitea instance identifier or URL — and the description gives no hint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ("Get details of a specific branch") and adds what the response contains — latest commit and protection settings. It is clearly distinguishable from create/delete branch siblings, though it does not name them explicitly.

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 mention of prerequisites such as authentication for private repositories, and no routing to alternatives like gitea_get_tree or gitea_compare when the agent actually needs ancestry or diff information.

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