Skip to main content
Glama

Open a draft pull request

create_pull_request

Open any change as a draft PR on a new branch in one of the repos connected to Fictura. Optionally tie it to an issue. Nothing under .github/. Needs "Let MCP keys open pull requests".

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

Input Schema

NameRequiredDescriptionDefault
baseNoTarget branch; default: the repo's default branch
bodyYes
repoYesowner/repo
filesYes
titleYes
issue_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare the safety profile (not read-only, open-world, non-idempotent, non-destructive); the description adds genuinely new behavior: the PR is opened as a draft on a new branch, files under .github/ are excluded, and a specific permission toggle is required. It stops short of saying what is returned or whether the draft can be later published.

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?

Three short sentences, front-loaded with the core action and followed by the optional issue link and file constraint. The trailing permission note is fragmentary but still earns its place.

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 mutation tool with 6 parameters, a nested files array, low schema coverage, and no output schema, key details are missing: what the call returns, whether title/body are validated beyond lengths, and when to choose patch over content. Adequate but with clear gaps.

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 only 33%, so the description carries extra burden. It clarifies that issue linkage is optional via issue_id and constrains files with the .github/ exclusion, but adds nothing about repo, title, body, or the patch-vs-content tradeoff in the nested files object.

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 any change as a draft PR on a new branch in one of the repos connected to Fictura." Scope (draft, new branch, connected repos) is clear enough to separate it from read tools like get_pull_request_status, though it does not explicitly contrast with siblings such as create_fix_pr.

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 (when you have a change to propose) and it names a prerequisite, the "Let MCP keys open pull requests" permission. It gives no explicit when-not guidance or routing to alternative PR-creation tools like create_fix_pr, so the agent must infer selection.

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