Skip to main content
Glama

Analyze Commit Patterns

analyze_commit_patterns
Read-onlyIdempotent

Analyzes commit history to uncover recurring patterns and trends, helping you understand development activity and make informed decisions.

Instructions

Analyze patterns in a list of commits or recent history

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

Input Schema

NameRequiredDescriptionDefault
maxCountNoMaximum number of commits to analyze. Default: 50
use_test_dbNo

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
detailsNoAdditional error context
successYes
analysisNo
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv9.1.0
    • changedInput schema / properties / maxCount / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "string"
      +]
  2. First observedv9.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that: it does not say what analysis is produced, whether results are cached or computed live, or how large histories are handled. With annotations doing the heavy lifting, this contributes almost no marginal context.

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

Conciseness3/5

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

It is a single short sentence with no wasted words, which is structurally fine, but the brevity comes from under-specification rather than precision. Nothing is front-loaded beyond the tool's own name restated.

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

Completeness2/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 not be explained, but the tool's core semantics — what 'patterns' means and what the analysis answers — are left undefined. Combined with an undocumented parameter and no sibling differentiation, the definition is too thin for an analysis tool in a crowded commit/insights family.

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

Parameters2/5

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

Only 50% of parameters are documented in the schema; maxCount has a description plus default, while use_test_db has no description anywhere. The tool description does not compensate at all: it never mentions a count limit or a test-database mode, so the agent must guess what use_test_db does.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb is 'analyze' and the resource is 'patterns in commits', so the general intent is clear, but the description never says which patterns (frequency, authorship, timing, churn) or what form the analysis takes. It also fails to distinguish this tool from close siblings such as get_commit_history, search_commits, or get_repo_insights, all of which touch commit data.

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 when-to-use guidance, no exclusions, and no named alternative. The phrase 'a list of commits or recent history' vaguely implies two input modes, but the agent is given no rule for choosing this tool over get_commit_history or search_commits.

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