Skip to main content
Glama
HasanJahidul

Git Insight MCP

by HasanJahidul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

recent_work

Read-onlyIdempotent

Retrieve a summary of commits by an author within a time window, including files changed and line counts, to prepare standup reports or changelogs.

Instructions

Read-only. Standup / changelog helper: one author's commits in a time window with files touched and insertion/deletion totals. Defaults to the repo's user.name and the last 7 days. Pure local git; no network. Returns { author, since, commit_count, commits[] } where each commit has subject, date, files, insertions, deletions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoPath inside the target git repo. Defaults to the server's current working directory.
limitNoMaximum number of commits to return, newest first. Default 100.
sinceNoAny git date expression, e.g. `7 days ago`, `2026-05-01`, `last monday`. Default `7 days ago`.
authorNoAuthor name or email substring (passed to `git log --author`). Defaults to `git config user.name`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNo
authorNo
commitsNo
commit_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.3
    • changedInput schema / properties / author / description
      Previous value: -"Defaults to git config user.name"New value: +"Author name or email substring (passed to `git log --author`). Defaults to `git config user.name`."
    • addedInput schema / properties / cwd / description
      Added value: +"Path inside the target git repo. Defaults to the server's current working directory."
    • changedInput schema / properties / limit / description
      Previous value: -"Max commits to return (default 100)"New value: +"Maximum number of commits to return, newest first. Default 100."
    • changedInput schema / properties / since / description
      Previous value: -"Git date expression (default '7 days ago')"New value: +"Any git date expression, e.g. `7 days ago`, `2026-05-01`, `last monday`. Default `7 days ago`."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "author": {
+      "type": "string"
+    },
+    "commit_count": {
+      "type": "number"
+    },
+    "commits": {
+      "items": {
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "deletions": {
+            "type": "number"
+          },
+          "files": {
+            "type": "number"
+          },
+          "insertions": {
+            "type": "number"
+          },
+          "sha": {
+            "type": "string"
+          },
+          "subject": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "since": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description reinforces annotations with 'Read-only' and adds behavioral context like 'Pure local git; no network', which goes beyond the annotations. It also describes the output structure. No contradictions with annotations.

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?

The description is two sentences: the first succinctly defines purpose and scope, the second details the return format. Every word contributes meaningful information, no fluff or repetition.

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?

Given the tool's moderate complexity and the presence of an output schema in the description, the description covers defaults, return type, and key constraints. Minor omissions like the exact git command used are not critical for an AI agent.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds valuable default behavior information (e.g., author defaults to repo's user.name, since defaults to 7 days ago). This enriches the agent's understanding beyond the raw schema.

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 clearly states it's a read-only standup/changelog helper that shows one author's commits in a time window with file changes and insertion/deletion totals. This distinctively sets it apart from sibling tools like 'branch_hygiene' or 'co_change' by focusing on individual author activity.

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

Usage Guidelines4/5

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

The description implies usage scenarios (standup, changelog) and mentions defaults, but does not explicitly state when to avoid using it or compare it to sibling tools like 'who_touched' or 'commit_context'. However, the context is clear enough for an AI agent to infer appropriate use.

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