Skip to main content
Glama

Open a Git push for a service

create_push
Destructive

Open a Git push on a website, app, agent, or skill that exists: a branch of its repository, writable for one hour, that you push source to before you publish. Use it when you can run git with network access; it sends only what changed, so a large service publishes without carrying its files through the conversation. Otherwise publish with files. The service must exist first: create_service makes it.

A push needs the SHA-256 of a Git key that stays on your machine, as key_sha256; never send the key or put it in a command. This recipe makes a new key for this push in its own mode-600 file, never reusing one, and prints the file's path, then the hash: umask 077; d="$HOME/.config/valet/git-keys"; mkdir -p "$d"; chmod 700 "$d"; f=$(mktemp "$d/key.XXXXXX") && head -c 32 /dev/urandom | od -An -tx1 | tr -d ' \n' > "$f" && echo "$f" && (sha256sum 2>/dev/null || shasum -a 256) < "$f" | cut -d' ' -f1

The result carries a Git URL with no credential, the push's id and branch, the commit it starts from, the name and email to commit as, the limits, and two recipes that read your key from the file: clone the branch and edit, or push a directory as it stands. A push over the limits is refused. Run a recipe, then call publish_site, publish_app, publish_agent, or publish_skill with push: {id, commit}, where commit is the sha the recipe prints. When the push is published, delete this push's key file, and only it: rm -f "$VALET_GIT_KEY_FILE". Only you can publish a push you opened. The key writes only this push's branch, cannot force-push, and expires with the push. Calling again with the same idempotency_key and a different key_sha256 replaces the push's key, so the earlier key stops working for that push. A service holds ten open pushes at once. Requires connecting a Valet account.

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": {
      "name": "<name>",
      "key_sha256": "<key_sha256>"
    },
    "name": "create_push"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe website's, app's, agent's, or skill's name, as list_services shows it: the one to push to.
org_nameNoThe Valet organization it belongs to. Omit to use the organization the account joined first.
key_sha256YesThe SHA-256 of the new Git key you generated on your machine for this push, which the recipe in this tool's description prints second. The push accepts only that key. The key itself is never sent.
idempotency_keyNoAn opaque key of your choosing. Repeating a call with the same key returns the same push instead of opening a second one. A repeat with a different key_sha256 replaces the push's key, so the earlier key stops working for that push.

Output Schema

NameRequiredDescriptionDefault
orgYesName of the Valet organization the call acted in.
urlYesGit URL of the push branch. It holds no credential: the recipes authenticate with your key file.
nameNoName of the website, app, or agent the push is on. Absent for a skill push.
skillNoName of the skill the push is on. Absent for a website, app, or agent push.
branchYesThe push branch, draft/<push_id>. Your key writes only this branch.
limitsYesThe bounds a push published to this service must stay within. A push over them is refused.
push_idYesID of the push. Pass it to the publish tool as push.id.
commandsYesTwo shell recipes that read your key from its file. The first clones the branch so you can edit; the second pushes a directory as it stands. Each prints the commit sha to pass to the publish tool.
expires_atYesWhen the push and its key stop working, as an RFC 3339 time. Publish before then.
author_nameYesName to commit as.
base_commitYesCommit sha of main when the push opened. The branch starts here.
author_emailYesEmail to commit as.
active_commitNoCommit sha of the deployed release, or for a skill its latest version. Absent when nothing is deployed or published.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"The website's, app's, agent's, or skill's name."New value: +"The website's, app's, agent's, or skill's name, as list_services shows it: the one to push to."
  2. Changed1 schema field changed
    • changedInput schema / properties / key_sha256 / description
      Previous value: -"The SHA-256 of the Git key you generated on your machine, which the recipe in this tool's description prints. The push accepts only that key. The key itself is never sent."New value: +"The SHA-256 of the new Git key you generated on your machine for this push, which the recipe in this tool's description prints second. The push accepts only that key. The key itself is never sent."
  3. Changed21 schema fields changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"An opaque key of your choosing. Repeating a call with the same key returns the same push instead of opening a second one, and replaces the push's key_sha256, which makes a retry safe."New value: +"An opaque key of your choosing. Repeating a call with the same key returns the same push instead of opening a second one. A repeat with a different key_sha256 replaces the push's key, so the earlier key stops working for that push."
    • changedInput schema / properties / key_sha256 / description
      Previous value: -"Required. The lowercase hex SHA-256 (64 characters) of the Git key you generated on your machine. Never send the key itself."New value: +"The SHA-256 of the Git key you generated on your machine, which the recipe in this tool's description prints. The push accepts only that key. The key itself is never sent."
    • addedInput schema / properties / key_sha256 / pattern
      Added value: +"^[0-9a-f]{64}$"
    • addedInput schema / required
      Added value: +[
      +  "name",
      +  "key_sha256"
      +]
    • addedOutput schema / properties / active_commit / description
      Added value: +"Commit sha of the deployed release, or for a skill its latest version. Absent when nothing is deployed or published."
    • addedOutput schema / properties / author_email / description
      Added value: +"Email to commit as."
    • addedOutput schema / properties / author_name / description
      Added value: +"Name to commit as."
    • addedOutput schema / properties / base_commit / description
      Added value: +"Commit sha of main when the push opened. The branch starts here."
    • addedOutput schema / properties / branch / description
      Added value: +"The push branch, draft/<push_id>. Your key writes only this branch."
    • addedOutput schema / properties / commands / description
      Added value: +"Two shell recipes that read your key from its file. The first clones the branch so you can edit; the second pushes a directory as it stands. Each prints the commit sha to pass to the publish tool."
    • addedOutput schema / properties / expires_at / description
      Added value: +"When the push and its key stop working, as an RFC 3339 time. Publish before then."
    • addedOutput schema / properties / limits / description
      Added value: +"The bounds a push published to this service must stay within. A push over them is refused."
    • addedOutput schema / properties / limits / properties / max_file_bytes / description
      Added value: +"Most bytes one file may hold. Absent when the installation sets no limit."
    • addedOutput schema / properties / limits / properties / max_files / description
      Added value: +"Most files a push may hold. Absent when the installation sets no limit."
    • addedOutput schema / properties / limits / properties / max_total_bytes / description
      Added value: +"Most bytes all files together may hold. Absent when the installation sets no limit."
    • addedOutput schema / properties / name / description
      Added value: +"Name of the website, app, or agent the push is on. Absent for a skill push."
    • addedOutput schema / properties / org / description
      Added value: +"Name of the Valet organization the call acted in."
    • addedOutput schema / properties / push_id / description
      Added value: +"ID of the push. Pass it to the publish tool as push.id."
    • addedOutput schema / properties / skill / description
      Added value: +"Name of the skill the push is on. Absent for a website, app, or agent push."
    • addedOutput schema / properties / url / description
      Added value: +"Git URL of the push branch. It holds no credential: the recipes authenticate with your key file."
    • changedOutput schema / required
      Previous value: -[
      -  "org",
      -  "push_id",
      -  "url",
      -  "branch",
      -  "base_commit",
      -  "active_commit",
      -  "expires_at",
      -  "author_name",
      -  "author_email",
      -  "limits",
      -  "commands"
      -]New value: +[
      +  "org",
      +  "push_id",
      +  "url",
      +  "branch",
      +  "base_commit",
      +  "expires_at",
      +  "author_name",
      +  "author_email",
      +  "limits",
      +  "commands"
      +]
  4. Changed2 schema fields changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"An opaque key of your choosing. Repeating a call with the same key returns the same push, with a fresh URL, instead of opening a second one, which makes a retry safe."New value: +"An opaque key of your choosing. Repeating a call with the same key returns the same push instead of opening a second one, and replaces the push's key_sha256, which makes a retry safe."
    • addedInput schema / properties / key_sha256
      Added value: +{
      +  "description": "Required. The lowercase hex SHA-256 (64 characters) of the Git key you generated on your machine. Never send the key itself.",
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "active_commit": {
      +      "type": "string"
      +    },
      +    "author_email": {
      +      "type": "string"
      +    },
      +    "author_name": {
      +      "type": "string"
      +    },
      +    "base_commit": {
      +      "type": "string"
      +    },
      +    "branch": {
      +      "type": "string"
      +    },
      +    "commands": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    },
      +    "expires_at": {
      +      "type": "string"
      +    },
      +    "limits": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "max_file_bytes": {
      +          "type": "integer"
      +        },
      +        "max_files": {
      +          "type": "integer"
      +        },
      +        "max_total_bytes": {
      +          "type": "integer"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "org": {
      +      "type": "string"
      +    },
      +    "push_id": {
      +      "type": "string"
      +    },
      +    "skill": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "push_id",
      +    "url",
      +    "branch",
      +    "base_commit",
      +    "active_commit",
      +    "expires_at",
      +    "author_name",
      +    "author_email",
      +    "limits",
      +    "commands"
      +  ],
      +  "type": "object"
      +}
  6. Changed2 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"The service's name, for a push to a website, app, or agent. Pass name or skill, not both."New value: +"The website's, app's, agent's, or skill's name."
    • removedInput schema / properties / skill
      Removed value: -{
      -  "description": "The skill's name, for a push to an organization skill. Pass name or skill, not both.",
      -  "type": "string"
      -}
  7. Changed3 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Required. The service's name."New value: +"The service's name, for a push to a website, app, or agent. Pass name or skill, not both."
    • addedInput schema / properties / skill
      Added value: +{
      +  "description": "The skill's name, for a push to an organization skill. Pass name or skill, not both.",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "name"
      -]
  8. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only mark this as a non-read-only, destructive, non-idempotent write; the description goes far beyond, disclosing the one-hour writable window, the ten-open-pushes limit, key scoping ('writes only this push's branch, cannot force-push, and expires with the push'), refusal over limits, account-connection requirement, and the key-replacement consequence of a repeated idempotency_key. The idempotency_key behavior is a useful addition to idempotentHint=false rather than a contradiction, since it describes conditional deduplication rather than natural idempotence.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the primary when-to-use decision are front-loaded in the opening sentences, and the operational details follow in a workable order. The embedded shell recipe is long and dense, but it is load-bearing for correct invocation rather than filler; the only mild redundancy is restating the return contents alongside an existing output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter mutation with an output schema, the description covers everything an agent needs: prerequisites, credential handling, limits, expiry, post-call workflow, and cleanup ('delete this push's key file, and only it'). Describing the returned URL, branch, and commit is slightly redundant with the output schema but is not harmful.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds genuinely new meaning: it explains how key_sha256 is produced (a specific key-generation recipe and that the hash is the second printed value), warns never to transmit the key, and clarifies that 'name' matches what list_services shows. The idempotency_key explanation largely restates the schema field, keeping this below 5.

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 first sentence names a specific verb and resource — 'Open a Git push on a website, app, agent, or skill that exists' — and defines what the artifact is: 'a branch of its repository, writable for one hour, that you push source to before you publish.' That scope makes it unmistakably distinct from the sibling publish_site/publish_app/publish_agent/publish_skill tools, which consume a push rather than open one.

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?

It states the selecting condition explicitly ('Use it when you can run git with network access'), the reason ('it sends only what changed'), and the alternative when the condition fails ('Otherwise publish with files'). It also gives a prerequisite ('The service must exist first: create_service makes it') and names the four downstream publish tools to call afterwards.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources