Skip to main content
Glama
jolfr

Commit Helper MCP

by jolfr

get_git_implementation_info

Check Git implementation details and available features to determine compatibility and functionality for commit operations.

Instructions

Get information about the current git implementation and available features.

Returns: Dict containing: - git_enabled: Whether git operations are available - implementation: Current git implementation ("GitPython") - enhanced_features: Whether enhanced features are available - features: Dict of available feature flags

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler decorated with @mcp.tool(), executes by calling service.get_git_implementation_info() and wrapping in success response.
    @mcp.tool()
    @handle_errors(log_errors=True)
    def get_git_implementation_info() -> Dict[str, Any]:
        """
        Get information about the current git implementation and available features.
    
        Returns:
            Dict containing:
            - git_enabled: Whether git operations are available
            - implementation: Current git implementation ("GitPython")
            - enhanced_features: Whether enhanced features are available
            - features: Dict of available feature flags
        """
        result = service.get_git_implementation_info()
        return create_success_response(result)
  • Helper method in CommitzenService facade that provides the actual git implementation information based on service state.
    def get_git_implementation_info(self) -> Dict[str, Any]:
        """Get information about the current git implementation."""
        return create_success_response(
            {
                "git_enabled": self.git_enabled,
                "implementation": self.git_implementation,
                "enhanced_features": self.git_enabled,  # GitPython always has enhanced features
                "features": {
                    "basic_operations": self.git_enabled,
                    "enhanced_status": self.git_enabled,
                    "detailed_diffs": self.git_enabled,
                    "commit_statistics": self.git_enabled,
                    "repository_analytics": self.git_enabled,
                },
            }
        )
  • The @mcp.tool() decorator registers this function as an MCP tool.
    @mcp.tool()
    @handle_errors(log_errors=True)
    def get_git_implementation_info() -> Dict[str, Any]:
        """
        Get information about the current git implementation and available features.
    
        Returns:
            Dict containing:
            - git_enabled: Whether git operations are available
            - implementation: Current git implementation ("GitPython")
            - enhanced_features: Whether enhanced features are available
            - features: Dict of available feature flags
        """
        result = service.get_git_implementation_info()
        return create_success_response(result)
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by specifying the return structure in detail. It discloses that this is a read-only informational tool (implied by 'Get information'), though doesn't mention potential side effects, performance characteristics, or authentication requirements.

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?

Perfectly structured with a clear purpose statement followed by detailed return format. Every sentence adds value: the first states what it does, the second explains what it returns. No redundant information.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 0-parameter tool with output schema (implied by the detailed return description), this description is complete. It explains both the purpose and the return values thoroughly, making the tool's behavior fully understandable without needing additional context.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description correctly indicates no parameters needed by not mentioning any, which aligns perfectly with the empty input 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 the verb 'Get' and resource 'information about the current git implementation and available features'. It distinguishes from sibling tools like 'get_git_status' or 'get_branch_analysis' by focusing on implementation metadata rather than repository state or analysis.

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?

The description implies usage when needing to check git availability and capabilities, but doesn't explicitly state when to use this vs alternatives like 'health_check' or 'refresh_configuration'. No exclusions or prerequisites are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jolfr/commit-helper-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server