GPT Commander

git_commit_prepare

Stage selected files and receive a commit prep summary, clarifying what changes are ready to commit.

Instructions

Stage changes (optional) and return a commit prep summary

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "git_commit_prepare"
  }
}

Input Schema

Name	Required	Description	Default
`cwd`	No
`paths`	No
`stageAll`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It mentions optional staging, implying mutation, but does not disclose what the summary contains, whether the tool modifies the repository, what side effects staging has, or any permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is concise and front-loaded, but it is under-specified. It earns its place but does not deliver enough information to be considered well-rounded for a tool with multiple parameters and no annotations.

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

Completeness2/5

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

Given the tool has 3 parameters, no annotations, and no output schema, the description is incomplete. It mentions staging and a summary but omits return value format, side effects, and parameter semantics, making it insufficient for safe and correct invocation.

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

Parameters1/5

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

Schema description coverage is 0% and the description provides no explanation of the three parameters (cwd, paths, stageAll). It does not clarify how paths and stageAll interact or that cwd sets the working directory, leaving the agent entirely dependent on the parameter names.

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?

The description uses specific verbs ('stage', 'return a summary') and names the resource (commit prep summary). It distinguishes from sibling tools like git_status and git_diff by focusing on staging and preparing a commit, though 'commit prep summary' is somewhat vague.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as git_status or git_diff. The phrase 'Stage changes (optional)' implies flexibility but does not state explicit use cases or exclusions.

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