Skip to main content
Glama

git_pull

Pull changes from a remote Git repository to update your local branch. Specify the remote name, branch, and repository path.

Instructions

Pull changes from remote

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
remoteNoRemote name
branchNoBranch name
cwdNoRepository path

Implementation Reference

  • The gitPull method that executes the pull command using gitCommand helper. Pulls from the specified remote (default 'origin') and optionally a specific branch.
    async gitPull(args: GitPullArgs): Promise<ToolResult> {
      const { remote = 'origin', branch, cwd } = args;
      const pullArgs = ['pull', remote];
      if (branch) pullArgs.push(branch);
      
      return await this.gitCommand(pullArgs, cwd);
    }
  • GitPullArgs interface defining input schema for git_pull: remote (optional, default 'origin'), branch (optional), cwd (optional).
    export interface GitPullArgs extends GitCommandArgs {
      remote?: string;
      branch?: string;
    }
  • src/index.ts:195-196 (registration)
    Registration of git_pull handler in the main tool router - dispatches to gitService.gitPull(args).
    case 'git_pull':
      return await this.gitService.gitPull(args);
  • Tool definition schema for git_pull with name, description, and inputSchema properties (remote, branch, cwd).
    {
      name: 'git_pull',
      description: 'Pull changes from remote',
      inputSchema: {
        type: 'object',
        properties: {
          remote: { type: 'string', description: 'Remote name' },
          branch: { type: 'string', description: 'Branch name' },
          cwd: { type: 'string', description: 'Repository path' },
        },
      },
    },
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention that git_pull performs a merge or rebase, which could cause conflicts or alter the working tree. This is a significant omission for a potentially destructive operation.

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?

The description is extremely concise, consisting of a single sentence. It wastes no words, but the brevity comes at the cost of missing important details. However, it is well-structured for a minimal tool.

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

Completeness2/5

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

Given the absence of an output schema and annotations, the description should provide more context about behavior, return values, and side effects. It only states the action without explaining the merging process, conflict resolution, or any output.

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?

The input schema has 100% description coverage for all three parameters (remote, branch, cwd). The description adds no additional semantic meaning beyond the schema, meeting the baseline for this dimension.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Pull changes from remote' is a standard Git operation, clearly indicating the verb and resource. However, it does not explicitly differentiate from hypothetical sibling tools like git_fetch, but in the context of the sibling list, it stands out from git_push and others.

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

Usage Guidelines2/5

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

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives like git_fetch or git_merge, nor does it mention prerequisites like staged changes or network connectivity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agentics-ai/code-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server