Skip to main content
Glama

git_pull

Destructive

Fetch remote commits and merge them into a place's mirror to restore files on a new machine, then sync changes into Studio. Commit or check status first; conflicts stop the merge.

Instructions

Fetch the remote's commits and merge them into the mirror, for example to restore a place's files on a new machine. Merged changes overwrite files in the mirror, and the file sync carries them into Studio. Commit or check git_status first; a conflict stops the merge.

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

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
Behavior5/5

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

Annotations already flag destructive=true and openWorld=true, but the description adds what those annotations cannot: merged changes overwrite mirror files, the file sync propagates them into Studio, and a conflict halts the merge. It also discloses the ordering requirement relative to commit/status, which is real operational context rather than a restatement of hints.

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 sentences, front-loaded with the action, then the consequence, then the prerequisite. Every sentence carries distinct information and there is no redundant wording.

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-parameter mutation with no output schema, the description covers consequences, propagation into Studio, prerequisites and conflict behavior. It does not say how to proceed after a conflict (e.g., which sibling to use or whether a retry is safe), which is the remaining gap.

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 description coverage is 100% and the single place parameter is fully documented in the schema, so the baseline is 3. The description never mentions the parameter, adding no defaulting or ID-vs-name guidance beyond what the schema already states.

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 ('Fetch the remote's commits and merge them into the mirror') and adds an intent example ('restore a place's files on a new machine'). An agent can separate this from git_push, git_status and git_log without opening any schema.

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?

Gives a concrete use case (restoring a place on a new machine) plus an explicit prerequisite: commit or check git_status first. It stops short of naming when to prefer a sibling such as pull_place, so the when-not side is only partly covered.

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