Gitmoji Commit MCP

git_commit

Create git commits with emoji types per the conventional commit standard. Validates staged changes exist and formats the commit message before committing.

Instructions

Create a git commit following the emoji-commit convention. Validates staged changes exist, formats the message, and creates the commit.

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": {
      "type": "<type>",
      "title": "<title>"
    },
    "name": "git_commit"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	The commit type (feat, fix, docs, etc.)
`scope`	No	Optional scope (e.g., #123, auth, api)
`title`	Yes	Brief description in imperative mood (50 chars max)
`breaking`	No	Whether this is a breaking change
`repo_path`	No	Optional path to the git repository. Use when MCP server runs outside your project directory.
`description`	No	Optional detailed explanation

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 9, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description must carry the full burden. It does disclose important behaviors: it validates staged changes, formats the message, and creates the commit. However, it omits other relevant traits such as failure modes, commit hooks, or repository configuration needs, so it provides only partial transparency.

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 only two sentences, front-loaded with the main action. It avoids unnecessary detail and every sentence adds value, even though 'creates the commit' appears twice.

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 tool with 6 parameters and no output schema, the description covers the core purpose and a key prerequisite, but does not explain return values or broader context like repo_path usage. Still, the schema comprehensively documents parameters, so the description is reasonably complete.

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 100%, so the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already provides; it does not elaborate on how parameters like 'scope' or 'breaking' are used.

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 specific action: 'Create a git commit following the emoji-commit convention.' It also names the resource (git commit) and differentiates from sibling tools that only format/validate/suggest messages by emphasizing the creation step: 'creates the commit.'

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

Usage Guidelines4/5

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

The description gives clear context by noting the prerequisite of staged changes ('Validates staged changes exist') and the workflow (format then create). However, it does not explicitly mention alternatives like git_format_message or state when not to use this tool, so it stops short of a 5.

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

Deploy Server