Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

git_commit

Destructive

Create a Git commit with a required message after GUI approval, enabling controlled version checkpoints while noting that hooks may run.

Instructions

Create a Git commit with an explicit message; requires GUI approval. Hooks may execute.

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

Input Schema

NameRequiredDescriptionDefault
messageYesCommit message, maximum 300 chars

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=false, so the safety profile is covered; the description still adds genuinely non-obvious behavior: GUI approval gating and the possibility that hooks execute. It omits a key behavioral fact — whether the commit captures all working-tree changes or only staged ones.

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 short clauses, zero filler, and the operation is front-loaded before the caveats about approval and hooks.

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

Completeness3/5

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

For a destructive mutation with no output schema, the description covers approval and hook side effects but leaves the agent unsure what content the commit will include and what a failure or hook rejection looks like — a meaningful gap for a write operation.

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 coverage is 100% for the single parameter, including the 300-char limit, so the schema carries the semantics. The description only echoes "explicit message" without adding format, validation, or error behavior beyond that.

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?

States a specific verb and resource ("Create a Git commit") plus a scope qualifier ("with an explicit message"), which cleanly separates it from siblings like git_stage, git_diff, and git_log.

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?

It discloses a real prerequisite ("requires GUI approval") that tells the agent what will happen at invocation time, but it gives no explicit when-to-use guidance, no mention of sequencing (e.g., staging first), and no alternatives.

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