devflow

Overview Schema Source Related Servers Discussions Admin

df_pr

Create a pull request for the current branch on GitHub or a merge request on GitLab, using a provided title and description.

Instructions

Crear un Pull Request (GitHub) o Merge Request (GitLab) para la rama actual.

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>"
    },
    "name": "df_pr"
  }
}

Input Schema

Name	Required	Description	Default
`body`	No	Descripcion del PR/MR
`title`	Yes	Titulo del PR/MR

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.15Sep 20, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that the tool creates a PR/MR, but does not mention side effects, authentication requirements, whether it pushes the branch, or what happens if a PR already exists.

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 filler. It efficiently conveys the action, target platform, and branch scope.

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

Completeness4/5

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

For a simple two-parameter creation tool with complete schema descriptions, the description is largely sufficient. It covers what is created and for which branch, though it does omit some contextual details about preconditions and side effects.

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 100%, so the title and body parameters are already documented in the schema. The tool description adds no additional parameter meaning, which matches the baseline of 3.

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

Purpose5/5

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

The description states a specific action ('Crear... Pull Request o Merge Request') and a clear scope ('para la rama actual'). It unambiguously identifies the resource being acted on and is distinct from siblings like df_merge or df_push.

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?

The description implies usage is appropriate when the current branch is ready for a PR/MR, but it does not explicitly state when to prefer this tool over alternatives, nor does it mention exclusions or preconditions such as needing a remote branch or avoiding duplicate PRs.

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