github-fetcher

GitHub commits

github_commits

Read-onlyIdempotent

List repository commits filtered by ref, path, author, or date range, returning short SHA, message, author, and date.

Instructions

List commits on a ref, optionally filtered by path, author, or date range. Returns short sha, message, author, and date.

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": {
      "repo": "<repo>"
    },
    "name": "github_commits"
  }
}

Input Schema

Name	Required	Description
`ref`	No	Branch, tag, or commit; defaults to the repository default branch
`page`	No	Page number, starting at 1
`path`	No	Only commits touching this path
`repo`	Yes	Repository in owner/name form
`fresh`	No	Bypass the local cache
`since`	No	ISO 8601 lower bound
`until`	No	ISO 8601 upper bound
`author`	No	GitHub login or email to filter by
`per_page`	No	Items per page, default 20

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 1, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the return shape (short sha, message, author, date), which matters because there is no output schema. It omits caching behavior implied by the 'fresh' parameter and pagination semantics.

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 waste, with the core action front-loaded and the return shape following. Every clause earns its place.

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?

For a 9-parameter read tool with no output schema, the description covers the action, the filters, and the return fields. Minor gaps remain around pagination and cache behavior, but the schema carries those details.

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 every parameter is already documented in the schema. The description restates the filter dimensions (path, author, date range) without adding format or syntax detail beyond what the schema provides, which is the baseline case.

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 and resource ('List commits on a ref') plus the filter dimensions, so the agent knows exactly what the tool returns. It does not explicitly contrast with any sibling, but no sibling tool covers commits, so the risk of confusion is low.

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 implied by the description ('optionally filtered by path, author, or date range'), but there is no explicit when-to-use/when-not guidance or reference to alternatives such as github_search_code or github_file for related lookups.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.