Push local commits to a remote repository, with options to specify branch and remote.
Push commits to remote repository.
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"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| branch | No | ||
| remote | No | origin |
Changes observed during successful MCP inspections.
v3.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of behavioral disclosure, but it only states the obvious operation. It doesn't mention what happens if there are no commits, whether it pushes to the current branch, or any prerequisites.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is immediately understandable and contains no redundant information. It is appropriately brief for the operation name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has two optional parameters and no output schema, the description should provide more operational context, such as defaults for branch and remote, or behavior when parameters are omitted. It falls short of being complete, though it's understandable for a standard git operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has two parameters (branch and remote) with no descriptions, and schema coverage is 0%. The description mentions 'remote repository' but doesn't explain the branch parameter or defaults, adding minimal value beyond parameter names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool pushes commits to a remote repository, using a specific verb and resource. It differentiates from sibling tools like git_commit and git_pull by focusing on the push action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like git_sync or git_auto_sync_toggle. No exclusions or alternative references are given, leaving the agent to infer usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.