Skip to main content
Glama
Sign In
patchwork-os

patchwork-os

by Oolab-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

gitPush

Destructive

Push current branch to a remote Git repository with options for upstream tracking and force push (blocked on main/master).

Instructions

Push the current branch to a remote. Use setUpstream: true on the first push. Force push uses --force-with-lease. Blocked on main/master.

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": "gitPush"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoForce push with --force-with-lease. Blocked on main/master. Default: false.
branchNoBranch to push (default: current branch)
remoteNoRemote name (default: origin)
setUpstreamNoSet the upstream tracking branch (-u). Use on first push of a new branch. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations indicate destructiveHint=true, but description adds key behavioral traits: force push uses --force-with-lease (safer) and push is blocked on main/master. This goes beyond annotations to convey important constraints and safety behavior.

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 concise sentences: first states purpose, second gives setUpstream usage, third explains force push. No unnecessary words, front-loaded with core action.

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?

Covers all critical aspects: purpose, parameter usage, constraints (blocked branches), and safety (force-with-lease). Lacks mention of error handling or output, but given no output schema and tool simplicity, it's nearly complete.

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

Parameters5/5

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

Input schema has 100% description coverage, yet description adds value by specifying concrete usage for setUpstream ('Use on first push of a new branch') and force ('Blocked on main/master'). Enhances understanding beyond schema.

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?

Description clearly states 'Push the current branch to a remote' with specific verb and resource. It distinguishes from sibling tools like gitPull and gitCommit by focusing on push operation and providing specific behaviors (setUpstream, force push).

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

Usage Guidelines4/5

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

Provides explicit guidance on when to use setUpstream ('Use setUpstream: true on the first push') and when force push is blocked ('Blocked on main/master'). Does not directly name alternative tools but context (siblings) implies when not to use this tool.

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

Deploy Server

Other Tools