Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: List pr reviews

gitea_list_pr_reviews
Read-only

List all reviews on a Gitea pull request by specifying site, owner, repo, and PR number to inspect review feedback and approval status.

Instructions

[UNIFIED] List all reviews on a pull request.

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

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

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, so the description adds almost nothing on the behavioral side. It does not mention pagination, result ordering, whether drafts or pending reviews are included, or any auth/site requirements for the 'site' parameter. 'List all' at least signals no filtering, which is a small contribution.

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 short sentence, front-loaded with the verb and resource, with no filler prose. The '[UNIFIED]' prefix is noise that conveys nothing to an agent, which is the only real deduction here.

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?

With four required undocumented parameters, no output schema, and a mutation-free but otherwise opaque contract, the definition is under-specified for the complexity. An agent knows what the tool returns conceptually but not how to supply site/owner/repo or what the response shape will be.

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% across four required parameters, so the description carries the full burden and does not meet it. Only pr_number is implicitly explained by 'on a pull request'; site, owner, and repo receive no meaning at all, and there is no hint about expected formats or how the site value is chosen.

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 reviews on a pull request.' That is unambiguous about what the tool returns. It does not, however, distinguish itself from adjacent siblings such as gitea_list_pr_comments or gitea_create_pr_review, leaving the agent to infer that reviews are different from comments.

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 guidance on when to use this tool versus alternatives. It does not say to use it before requesting reviewers, after a review has been created, or how it differs from listing PR comments or commits. The agent must infer the usage context from the name alone.

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