Skip to main content
Glama
Sign In
Copilot Desktop MCP

Copilot Desktop MCP

by avianhermana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Pull Git Update

pull_git_update

Pull updates from a GitHub repository using git pull origin main, with automatic rollback protection if the pull fails.

Instructions

Pull the latest updates from the GitHub repository (git pull origin main) with automatic rollback protection.

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

Input Schema

NameRequiredDescriptionDefault
auto_restartNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It usefully discloses the exact git command and 'automatic rollback protection', but it does not explain what rollback protects against, whether the working tree is modified, how conflicts are handled, or what the default `auto_restart` behavior does.

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?

The description is a single front-loaded sentence with no redundancy. The command and rollback note both add useful information without padding.

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?

An output schema exists, so return values need not be explained. However, for a mutation tool with no annotations and an undocumented parameter, the description omits essential operational context: side effects, restart behavior, conflict handling, and when to prefer `check_git_updates` first.

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

Parameters1/5

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

The single parameter `auto_restart` has 0% schema description coverage and is not mentioned at all in the description. The default value is visible in the schema, but the description adds no meaning about what restarting means or when an agent should set it to false.

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 states a specific verb and resource: pulling the latest updates from the GitHub repository, with the exact command `git pull origin main` and a safety behavior. It is reasonably distinguishable from `check_git_updates` because it pulls rather than checks, though it does not explicitly name that sibling.

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

Usage Guidelines3/5

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

Usage is implied by 'Pull the latest updates', but there is no explicit guidance on when to use this versus `check_git_updates`, `git_status`, or `apply_self_update`. The agent must infer that this is the mutation step after checking for updates.

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