Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

github_pr_create

Destructive

Open a GitHub pull request with the gh CLI by providing a title, description, and base branch, assuming the branch is already pushed and local approval is granted.

Instructions

Open a GitHub pull request using gh CLI. Requires local approval. Assumes branch has been pushed.

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": {
      "title": "<title>",
      "body": "<body>"
    },
    "name": "github_pr_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNoBase branch, e.g. mainmain
bodyYesPR description
titleYesPR title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=false, destructiveHint=true, openWorldHint=true, so the safety profile is covered. The description adds genuinely new context: the operation shells out to the gh CLI, needs local approval before executing, and assumes the head branch is already pushed. It does not say what happens on failure or whether the call is idempotent, keeping it below a 5.

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 short sentences, front-loaded with the action and followed by the two gating conditions. No filler or redundancy.

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

Completeness3/5

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

For a destructive, open-world mutation tool, the prerequisites and mechanism are covered, but with no output schema the description never says what is returned (e.g. PR number or URL), which an agent may need to chain into follow-up calls. A brief note on the result or the derived head branch would make it complete.

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?

All three parameters have schema descriptions at 100% coverage, so the schema carries the semantics. The description adds no parameter-level detail, such as that title/body are required or that the head branch is derived from the current branch rather than passed in. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Open a GitHub pull request') plus the mechanism ('using gh CLI'), which clearly separates it from read-only siblings like github_pr_list. It stops short of naming an alternative explicitly, but the write-vs-list distinction is unambiguous.

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?

Prerequisites are given ('Requires local approval', 'Assumes branch has been pushed'), which tells the agent the conditions under which calling will succeed. However, there is no explicit when-to-use vs when-not guidance and no pointer to branch/commit siblings that must run first.

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