Skip to main content
Glama
Sign In
Git Analytics MCP Server

Git Analytics MCP Server

by singhashish4000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_repository_overview

Analyze Git repository statistics, identify top contributors, and review recent activity to assess codebase health and development patterns.

Instructions

Get a comprehensive overview of the Git repository including stats, top contributors, and recent activity

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_repository_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoPath to the Git repository (defaults to current directory).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the tool 'Get[s] a comprehensive overview' but does not specify if this is a read-only operation, potential side effects, authentication needs, rate limits, or output format. For a tool with no annotations, this leaves significant behavioral gaps, though it implies a safe read operation without being explicit.

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 a single, efficient sentence that front-loads the key action and details without any wasted words. It is appropriately sized for the tool's complexity, making it easy for an agent to parse and understand quickly.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally adequate. It states the purpose but lacks details on behavioral traits, usage context, and output, which are needed for full completeness. However, it covers the basic intent, making it functional but with clear gaps in guidance and transparency.

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?

The input schema has 100% description coverage, with the 'path' parameter well-documented in the schema itself. The description adds no additional parameter semantics beyond what the schema provides, such as examples or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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?

The description clearly states the tool's purpose with specific verbs ('Get') and resources ('Git repository'), and it details what information is included ('stats, top contributors, and recent activity'). However, it does not explicitly differentiate from sibling tools like 'get_author_stats' or 'get_repository_stats', which might offer overlapping or complementary functionality, preventing a perfect score.

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?

The description provides no guidance on when to use this tool versus its siblings ('get_author_stats' and 'get_repository_stats'). It lacks explicit instructions on alternatives, prerequisites, or exclusions, leaving the agent to infer usage based on tool names alone, which is insufficient for clear decision-making.

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