Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Create pr comment

gitea_create_pr_comment

Add a comment to a Gitea pull request by specifying the site, owner, repository, PR number, and comment body.

Instructions

[UNIFIED] Add a comment to 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>",
      "body": "<body>"
    },
    "name": "gitea_create_pr_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
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.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the mutation and repeat-call semantics are covered structurally. The description adds nothing beyond that: no mention of required permissions, failure modes, or what happens on a locked/closed PR. The unexplained "[UNIFIED]" prefix consumes space without conveying behavior.

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

Conciseness3/5

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

The single sentence is front-loaded and free of padding, which is good. However, the bracketed "[UNIFIED]" tag is unexplained noise, and the brevity here reflects under-specification rather than disciplined editing.

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?

For a five-parameter mutation tool with zero schema descriptions and no output schema, the definition supplies none of the context an agent needs to call it correctly. Nothing explains parameter meaning, expected return values, or error conditions.

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% across five required parameters, and the description compensates for none of it. It never clarifies that site identifies the Gitea instance, that owner/repo scope the repository, that pr_number is the PR index, or that body is the markdown comment text — all of which an agent must guess.

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 ("Add a comment to a pull request"), which is enough to distinguish it from listing or reviewing tools. It does not, however, explicitly differentiate itself from the close sibling gitea_create_issue_comment, which in Gitea operates on the same underlying object type.

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 such as gitea_create_pr_review or gitea_create_issue_comment, and no mention of prerequisites like authentication, permissions, or whether the PR must be open. The agent must infer all routing decisions.

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