Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: List pr files

gitea_list_pr_files
Read-only

List all changed files in a pull request with additions/deletions counts to assess review scope and code impact.

Instructions

[UNIFIED] List all changed files in a pull request with additions/deletions count.

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

Input Schema

NameRequiredDescriptionDefault
repoYes
siteYes
ownerYes
pr_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description contributes the shape of the result (file list with per-file additions/deletions), which is useful beyond the annotation, but it says nothing about pagination, truncation on large PRs, or auth/site requirements implied by the required 'site' parameter.

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?

A single, front-loaded sentence with no filler or redundancy. The only wasted token is the unexplained "[UNIFIED]" marker, which costs clarity without adding 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-only listing tool this is close to adequate: the resource and the returned fields are named, and no output schema exists to defer to. However, with four required and undocumented parameters (notably 'site'), the definition leaves meaningful gaps an agent must guess at.

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% and all four parameters (site, owner, repo, pr_number) are required but completely undocumented. The phrase "in a pull request" at best hints at pr_number; there is no explanation of what 'site' means (instance URL vs. alias) or how owner/repo are scoped, so the description fails to compensate for the coverage 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 and resource ("List all changed files in a pull request") and adds what the results contain (additions/deletions count). It is clearly distinguishable from siblings like gitea_list_pr_commits or gitea_list_pr_comments. The ambiguous "[UNIFIED]" prefix adds no differentiating meaning, and the boundary versus gitea_get_pr_diff is never stated.

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 exclusions, and no mention of the closest alternative (gitea_get_pr_diff, which also concerns PR changes). The agent must infer from the name alone whether to call this or the diff tool.

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