Skip to main content
Glama
Sign In
forgejo-mcp

forgejo-mcp

by jerdog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List review comments

list_pull_request_review_comments
Read-only

Fetch inline comments from a specific pull request review to inspect code feedback using owner, repo, pull request number, and review ID.

Instructions

List inline comments of a specific review.

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": {
      "owner": "<owner>",
      "repo": "<repo>",
      "index": "<index>",
      "review_id": "<review_id>"
    },
    "name": "list_pull_request_review_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository name
indexYesPull request number
ownerYesRepository owner (user or organization)
review_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that results are scoped to 'inline comments' of a single review, which is useful scoping context, but says nothing about pagination, ordering, or how inline comments differ from review summary comments.

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 tight sentence with no filler, and the resource scope is front-loaded. It is efficient but so terse that it omits any operational detail, leaving it slightly under-specified rather than optimally concise.

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 four-parameter filtered-list tool with no output schema, the definition is minimally adequate: it identifies the target of the listing but omits pagination behavior, ordering, and any hint about return shape. It covers the essentials but leaves clear gaps.

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

Parameters3/5

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

Schema coverage is 75% and the schema documents owner, repo, and index, leaving review_id undocumented. The description's 'of a specific review' loosely signals the review_id parameter but adds no format or sourcing detail. With the schema covering most parameters, the baseline 3 applies.

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?

States a specific verb (List) plus resource (inline comments of a specific review), so the agent knows it returns inline review comments rather than review bodies or issue comments. It is clear but never explicitly names the sibling it differs from, such as list_pull_request_reviews or list_issue_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?

The description gives no when-to-use guidance, no prerequisites, and no alternatives. An agent must infer from the name that this is the tool for inline comments on an existing review rather than a general comment listing.

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