Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitea-getGiteaRepositories

Read-onlyIdempotent

Fetches repositories from a Gitea account using its connection ID, so you can review available projects before deployment or automation.

Instructions

GET /gitea.getGiteaRepositories

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

Input Schema

NameRequiredDescriptionDefault
giteaIdYes

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?

The annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond the annotations: it does not state what the response contains (for example, a list of repositories), whether pagination applies, or how authentication is handled.

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?

The description is a single fragment with no wasted words, but it is under-specified rather than concise. There is no structure, no front-loaded explanation of purpose, and no supporting detail for the agent to use.

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?

The tool has one required parameter with 0% schema description coverage and no output schema, so the description carries the full burden of disclosure. It provides nothing, leaving the agent unable to determine scope, return shape, or parameter meaning.

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%: the single parameter giteaId is undocumented in both the schema and the description. The description should explain what giteaId identifies (a configured provider instance, a remote Gitea ID, and so on), but it 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 essentially the endpoint path "GET /gitea.getGiteaRepositories", which restates the tool name rather than explaining what the tool does. It does not say whether it returns all repositories for an instance, repositories for a user or organization, or how this differs from sibling tools like gitea-getGiteaBranches.

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 use this tool, no prerequisites, and no mention of alternatives. An agent would have to inspect the schema and guess the tool's role in the broader Gitea workflow.

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