Skip to main content
Glama
ai-commit-helper-mcp

ai-commit-helper-mcp

by mahshid

validate_commit_message

Checks a proposed commit message against the target repository's configured format and subject-length limit, returning validity and specific validation errors.

Instructions

Validate a proposed commit message against the target repository's configured format and maximum subject length. Returns whether the message is valid and a list of validation errors.

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": {
      "repositoryPath": "<repositoryPath>",
      "message": "<message>"
    },
    "name": "validate_commit_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYes
repositoryPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the return shape (a validity boolean plus a list of validation errors), which is genuinely useful given there is no output schema. It does not state that the operation is non-mutating, what happens if the repository has no configured rules, or whether a nonexistent repositoryPath errors.

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?

Two tight sentences, zero waste: the scope/behavior sentence comes first and the return contract second. Nothing is padded or restated from the tool name.

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?

For a two-parameter validator with no output schema and no annotations, the description covers purpose, scope, and return values adequately. Remaining gaps are edge-case behavior (missing config, invalid path) rather than anything needed to call it correctly.

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 0%, so the description must compensate. It does convey the roles of both parameters — message is the proposed text, repositoryPath is the repo whose format/length config is consulted — but adds no format guidance (path shape, whether it must exist, must it be a repo root).

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 a specific verb ('Validate') and resource ('a proposed commit message') and scopes it to the target repository's configured format and max subject length, which tells an agent this is a read-only check rather than a rule-creation step like create_commit_rules. It stops short of naming or contrasting any sibling explicitly, so it lands at 4 rather than 5.

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?

Usage is only implied: an agent can infer this is the pre-commit check to run before composing a message, and that repositoryPath selects which configuration applies. There is no explicit when-to-use or when-not-to-use statement, and no mention of how it relates to create_commit_rules or get_commit_context.

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