Skip to main content
Glama
Sign In
GitHub + Linear Dev Workflows

GitHub + Linear Dev Workflows

by r28ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

github_repos_compare_commits

Read-onlyIdempotent

Compare two Git refs or branches to see commits, ahead/behind status, and changed files, including across forks for pull request reviews.

Instructions

Compare two refs and get what is in one and not the other: the status, how far ahead or behind, the commits and the changed files. basehead is one string, 'main...my-feature', with three dots. Across forks, prefix each side with its owner.

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>",
      "basehead": "<basehead>"
    },
    "name": "github_repos_compare_commits"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoThe page number of the results to fetch. Defaults to 1.
repoYesThe name of the repository without the `.git` extension. The name is not case sensitive.
ownerYesThe account owner of the repository. The name is not case sensitive.
perPageNoThe number of results per page (max 100). Defaults to 30.
baseheadYesThe base and head to compare, as `BASE...HEAD` — for example `main...my-feature`. Across repositories in the same network, prefix each side with its owner: `octocat:main...contributor:fix`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), so the description earns credit for disclosing the response payload — status, ahead/behind, commit list, file changes. It omits any mention of pagination limits despite page/perPage existing, a minor gap.

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

Conciseness5/5

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

Two sentences, zero filler, front-loaded with the purpose and return content before the basehead syntax note. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 shoulders the return-value burden and does so by naming the comparison fields. What's missing is pagination behavior for a tool that clearly paginates (page/perPage present), but otherwise it is sufficient to call the tool correctly.

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 description coverage is 100%, so the schema already documents owner, repo, basehead, page and perPage. The description re-emphasizes the three-dot basehead format and cross-fork owner prefixing, which is helpful but largely duplicates the schema text; baseline 3 applies.

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?

States a specific verb and resource ('Compare two refs') and enumerates the output: status, ahead/behind counts, commits, and changed files. This is clearly distinguishable from siblings like github_repos_list_commits (single branch history) or github_pulls_list_files (one PR's files).

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?

The phrase 'get what is in one and not the other' implicitly conveys the use case, and fork-prefix guidance is given. However, it never states when to prefer this over alternatives such as github_repos_list_commits or github_pulls_get_diff, and gives no exclusions or prerequisites.

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