Skip to main content
Glama

Pull from GitHub

github_pull
Destructive

Pull from the linked GitHub base branch

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

Input Schema

NameRequiredDescriptionDefault
project_idNoProject id (or use session from use_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the agent knows this mutates state and reaches outside the sandbox. The description adds nothing on top of that: it does not say whether local/uncommitted changes are overwritten, whether the operation can fail on conflicts, or that repeated calls are not idempotent. For a destructive tool this is a meaningful omission.

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

Conciseness3/5

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

One short sentence with no wasted words, which is good, but the brevity comes at the cost of under-specification rather than being genuinely front-loaded information. It is concise without being informative.

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?

This is a destructive, non-idempotent, open-world mutation with no output schema, and the description supplies none of the context an agent needs to call it safely: what state changes, what is lost, and what happens on conflict. Given the complexity implied by the annotations, one sentence is not enough.

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?

There is a single optional parameter, project_id, and schema description coverage is 100%, including the hint to use a session from use_project. The description adds no additional meaning, but the schema already carries the burden, so the baseline of 3 applies.

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

Purpose3/5

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

"Pull from the linked GitHub base branch" names a verb and a source, so the general intent is inferable, but it never says what pulling actually does (fetch-and-merge into the project workspace? refresh a mirror?). It also gives no signal distinguishing it from the sibling github_sync, which an agent would reasonably confuse it with.

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?

There is no when-to-use guidance, no prerequisites (e.g. must a repo be linked first via github_link_repo?), and no mention of alternatives such as github_sync. The agent must guess the triggering condition entirely.

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