Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Get repository

gitea_get_repository
Read-only

Retrieve complete details for a specific Gitea repository by specifying its site, owner, and repository name. Use it to inspect repository information for management or automation tasks.

Instructions

[UNIFIED] Get details of a specific Gitea repository. Returns complete repository information.

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

Input Schema

NameRequiredDescriptionDefault
repoYes
siteYes
ownerYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.7/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds essentially nothing beyond that. "Returns complete repository information" is a vague promise; it does not say which fields are included, whether private repositories are reachable, or what happens when the repository does not exist. With annotations carrying the safety profile, the description should have contributed operational detail and did not.

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

Conciseness4/5

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

Two short sentences with no filler, and the core purpose is front-loaded. The unexplained "[UNIFIED]" prefix is noise that does not help an agent decide anything.

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

Completeness2/5

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

For a tool with three required, fully undocumented parameters and no output schema, the description should explain the identifiers and the return shape. Instead it offers only "complete repository information," leaving the agent to guess at the required inputs and the response.

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%: none of site, owner, or repo is documented anywhere. The description does not compensate, and the meaning of "site" in particular (instance URL vs. hostname vs. config key) is left entirely unclear. The parameter names are suggestive but not self-explanatory enough to rescue a total documentation gap.

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 states a specific verb+resource: "Get details of a specific Gitea repository." That is enough to separate it from gitea_create_repository, gitea_update_repository, and gitea_delete_repository by intent. It does not, however, draw an explicit boundary against other read tools such as gitea_get_branch or gitea_get_file.

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?

The description gives no when-to-use guidance, no prerequisites, and no description of when a different read tool would be the better choice. An agent must infer usage entirely from the tool 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