Skip to main content
Glama

git_commit

Commit changed files in a place's mirror repo to create a restore point for scripts and saved instances before risky edits, adding history without overwriting existing work.

Instructions

Stage and commit changes in a place's mirror repo, creating a restore point for scripts and saved instances. Only adds history; nothing is overwritten. Commits every change unless paths is given. Commit before risky edits so git_restore, git_revert and git_recover have something to go back to; git_push then copies it off this machine.

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
pathsNoCommit only these files. File path relative to the mirror folder, as git_status or git_log prints it, e.g. "ServerScriptService/Main.server.luau". Omit to commit everything that changed.
placeNoTarget place (PlaceId or project name) whose mirror repo to use. Defaults to the bound/sole connected place.
messageYesCommit message describing the change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / message / description
      Added value: +"Commit message describing the change."
    • addedInput schema / properties / paths / description
      Added value: +"Commit only these files. File path relative to the mirror folder, as git_status or git_log prints it, e.g. \"ServerScriptService/Main.server.luau\". Omit to commit everything that changed."
    • changedInput schema / properties / place / description
      Previous value: -"Target place (PlaceId or project name); defaults to the bound/sole place"New value: +"Target place (PlaceId or project name) whose mirror repo to use. Defaults to the bound/sole connected place."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description reinforces and explains this with 'Only adds history; nothing is overwritten', which tells the agent existing content is safe. It also adds scope behavior (default commits everything) and the local-vs-remote distinction versus git_push. It does not explicitly note that repeated calls create new commits (idempotentHint=false), which is the only notable disclosure gap.

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?

Three tight sentences, front-loaded with the action and its safety profile, then the scoping default, then the workflow guidance. Every clause carries distinct information; nothing is redundant filler.

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 three-parameter mutation tool with full schema coverage and safety annotations, the description covers purpose, safety, scope defaults, and how it fits the restore/push workflow. The one thing absent is any hint of the return value (e.g., a commit id) since no output schema exists, though that is minor for a commit 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%, so the schema already documents all three parameters, including the path format example and the place default. The only addition in the description is the default 'commits every change unless paths is given', which restates the schema's own 'Omit to commit everything that changed'. Baseline 3 is appropriate.

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 pair and resource: 'Stage and commit changes in a place's mirror repo', plus the effect ('creating a restore point for scripts and saved instances'). This clearly separates it from siblings like git_push (copies off machine), git_restore/git_revert/git_recover (go back), and git_status/git_diff (inspect).

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?

Gives an explicit when: 'Commit before risky edits so git_restore, git_revert and git_recover have something to go back to', and names the follow-on alternative: 'git_push then copies it off this machine'. The scoping default ('Commits every change unless paths is given') is also stated up front, so the agent knows the call shape without inferring.

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