Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Compare

gitea_compare
Read-only

Compare two commits, branches, or tags in a Gitea repository to retrieve commits and file diffs between a base and head reference.

Instructions

[UNIFIED] Compare two commits / branches / tags in a Gitea repository. Returns commits + file diffs between base and head (the Gitea compare endpoint).

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>",
      "base": "<base>",
      "head": "<head>"
    },
    "name": "gitea_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYes
headYes
repoYes
siteYes
ownerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.5/5.0
Behavior3/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. The description adds genuinely useful context beyond that by disclosing the return contents (commits plus file diffs) and tying it to the Gitea compare endpoint, but it says nothing about pagination, size limits, or behavior when base and head share no ancestry.

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?

Two sentences, front-loaded with the purpose and then the return shape, with no padding. The unexplained '[UNIFIED]' prefix and the backticks around base/head are minor noise that keeps it from a perfect score.

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?

With no output schema, the description usefully covers the return value, and comparison semantics are moderately clear. However, for a five-parameter tool whose schema documents nothing, leaving site, owner, and repo undefined means an agent still has to guess what each identifier refers to.

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 five required parameters, so the description carries the full explanatory burden. It only clarifies that base and head are refs being compared and that base comes first, while site, owner, and repo are left entirely unexplained beyond the phrase 'in a Gitea repository'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (compare) and resource (two commits / branches / tags in a Gitea repository) and states what comes back (commits plus file diffs). That is enough to distinguish it from sibling read tools like gitea_get_pr_diff or gitea_get_branch without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer it should call this when it needs a diff between two arbitrary refs, but the description never says when to prefer it over gitea_get_pr_diff and names no alternatives or exclusions. No prerequisites such as required refs being reachable are given.

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