Skip to main content
Glama
commit-check

commit-check-mcp

Official
by commit-check

validate_repository_state

Validate commit message, branch, author, and push safety of a local git repository in one read-only call. Ensure repository state meets your standards before commits or deployments.

Instructions

Validate the current repository state including latest commit message, active branch, author metadata, and optional push safety. Read-only validation. Reads git data (message, branch, author) from the local repository. Returns a structured result with overall status and per-check results.

Use this to validate the entire state of a local git repository in one call — ideal for pre-commit or CI hooks. Controls which checks run via boolean include_* flags. For validating arbitrary (non-repo) values, use validate_commit_context or individual validation tools instead.

Parameters:

  • repo_path (optional): Path to the git repository. If omitted, uses current working directory.

  • config (optional): Inline JSON config overrides on top of any loaded config file.

  • config_path (optional): Path to a custom commit-check TOML config file.

  • include_message (optional, default true): Whether to validate the latest commit message.

  • include_branch (optional, default true): Whether to validate the current branch name.

  • include_author (optional, default true): Whether to validate the latest commit author.

  • include_push (optional, default false): Whether to validate push safety.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
configNo
repo_pathNo
config_pathNo
include_pushNo
include_authorNo
include_branchNo
include_messageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Declares read-only validation, reads git data, returns structured results. Does not cover error behavior for missing repos or invalid paths, but sufficient given no 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?

Well-structured: purpose, behavior, usage, then parameter list. Front-loaded with key info. No unnecessary words.

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?

Covers all 7 parameters, returns structure, and differentiates from 7 siblings. Output schema exists, so return description is adequate.

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

Parameters5/5

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

With 0% schema coverage, description adds essential meaning: explains each parameter's purpose, defaults, and optionality. Provides context like 'if omitted, uses current working directory'.

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 validates the entire repository state (commit message, branch, author, push safety). It distinguishes from sibling tools by specifying that for non-repo values, other tools should be used.

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

Usage Guidelines5/5

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

Explicitly says 'Use this to validate the entire state of a local git repository in one call — ideal for pre-commit or CI hooks' and provides alternatives for other cases.

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/commit-check/commit-check-mcp'

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