Skip to main content
Glama

git_push

Pushes the current branch's commits to its remote as an off-machine backup of the place's scripts and saved instances using local Git credentials; set an upstream remote and commit first.

Instructions

Push the current branch's commits to its remote, as an off-machine backup of the place's scripts and saved instances. Sends data to the remote (for example GitHub) using your local git credentials. Needs a remote with an upstream branch: add one with git_remote first. Commit with git_commit before pushing.

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_push"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoTarget place (PlaceId or project name) whose mirror repo to use. Defaults to the bound/sole connected place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • 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, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds real context beyond them: data leaves the machine to a remote such as GitHub, and it authenticates with local git credentials. It does not mention failure modes like non-fast-forward rejection, which would have earned a 5.

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 short sentences, front-loaded with the action and purpose, then the two prerequisites. No filler and nothing repeated from the schema.

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 one-optional-parameter tool with no output schema and annotations covering the safety profile, the description covers purpose, auth, and prerequisites well. It omits what happens on rejection or conflict, a minor gap given the tool's simplicity.

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% and the single 'place' parameter is fully documented in the schema, so the baseline is 3. The description adds no meaning about the place parameter, though it does clarify that the pushed content is the current branch's commits.

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 ('Push the current branch's commits to its remote') and frames the intent (off-machine backup of scripts and saved instances), which distinguishes it from git_commit and git_remote by naming them as prerequisites rather than alternatives.

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?

Explicitly states prerequisites and routes the agent to the right siblings: 'Needs a remote with an upstream branch: add one with git_remote first. Commit with git_commit before pushing.' An agent knows exactly what must happen before calling this.

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