Skip to main content
Glama

commit_mine

Commit only your owned code hunks in a shared Git checkout, leaving others' changes untouched. Automatically releases file claims after commit.

Instructions

Commit ONLY your owned hunks as an ordinary git commit, leaving every other actor's changes untouched in the working tree. This is how each agent lands its own work in a shared checkout without sweeping up anyone else's. The committed files' claims auto-release, so no separate release call is needed. Preview it first with preview_mine.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actorNoactor id to act as. Auto-derived per connection when omitted (from the client name, e.g. cursor-3fa2), so naming is optional for a single agent. Pass an explicit id (your role/task name) when several subagents share one server — they have no ambient identity to tell them apart — or when you want a stable id across runs.
pathsNolimit the commit to these files (default: all your owned files) — a hard filter, so an unnamed orphan/leftover is never swept in
messageYesthe commit message
includeUnclaimedNoalso commit new/untracked files you authored but never claimed (default: false, so an unclaimed orphan is never swept into your commit while another actor is active)
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses key behaviors: commits only owned hunks, leaves other actors' changes untouched, and auto-releases claims. However, it does not mention failure modes (e.g., conflicts) or whether it pushes, but the main traits are well-covered.

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 four sentences, front-loaded with the core action, and every sentence adds value. It is efficient and avoids redundancy, earning a top score for conciseness.

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?

Given the complexity (4 parameters, no output schema, no annotations), the description provides sufficient context for the core use case. It explains the purpose, side effects (auto-release), and suggests a preview. It could mention edge cases or return values, but for a simple commit operation, it is adequate.

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%, with detailed descriptions for each parameter. The tool description does not add new per-parameter meaning beyond the schema, so it remains at the baseline. The description's context about 'owned hunks' and 'auto-release' provides general context but not parameter-specific guidance.

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 uses specific verbs and resources: 'Commit ONLY your owned hunks as an ordinary git commit'. It clearly distinguishes this tool from siblings like `preview_mine` (preview) and `claim` (claiming hunks), making its unique role evident.

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?

The description explicitly states when to use this tool (to land your own work in a shared checkout without affecting others' changes) and suggests previewing with `preview_mine`. It implicitly advises against using it when wanting to commit others' changes, providing clear context.

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/wkoverfield/quilt'

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