Skip to main content
Glama
Sign In
git-insights-mcp

git-insights-mcp

by andriilazor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

author_activity

Read-onlyIdempotent

Analyze Git author activity for a date range: retrieve commits, added lines, and deleted lines per author, excluding merges, ranked by commit count.

Instructions

Commits and added/deleted lines per author in the period (merge commits excluded), ranked by commits.

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": "author_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository alias, see the git-insights://repos resource
sinceNoStart of the period (ISO date, inclusive, UTC); omit for all
untilNoEnd of the period (ISO date, inclusive, UTC); omit for now

Output Schema

NameRequiredDescriptionDefault
repoYes
sinceYes
untilYes
authorsYesRanked by commits, then changed lines

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description is free to add the traits it does disclose: merge commits are excluded and results are ranked by commit count. Those are meaningful semantics an agent could not derive from the annotations or schema, though nothing is said about tie-breaking or result-size limits.

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?

A single tight sentence with the resource, scope, exclusion, and ordering front-loaded; every clause carries information and there is no filler.

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?

An output schema exists so return values need no explanation, annotations cover the safety profile, and all three parameters are schema-documented. The only gaps are operational details such as tie-breaking, truncation, and whether authors with zero commits appear.

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 repo/since/until are fully documented in the schema itself and the description need not repeat them. The description only gestures at 'the period', adding no format or boundary detail beyond what since/until already say.

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?

Names the exact resource (per-author commits and added/deleted lines), the scope (in the period), and the output ordering (ranked by commits), plus an explicit exclusion (merge commits). That is far more specific than a bare name, though it never contrasts itself with siblings like repo_summary or hotspots.

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 statement of when to reach for this tool versus the alternatives, no prerequisites, and no note on what happens with an empty period. The 'in the period' phrasing implies a time-boxed contribution report, but the agent must infer that on its own.

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