Skip to main content
Glama
Sign In

Exogram — Personal AI Agent & Workspace

by io.github.Richard-Ewing
OverviewDiscussionsAdmin

github_create_pr_draft

Draft a GitHub Pull Request proposal. Does NOT open or publish the PR without explicit user approval.

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>",
      "head": "<head>",
      "body": "<body>"
    },
    "name": "github_create_pr_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNoTarget base branch (default: "main").main
bodyYesDetailed PR description and change summary.
headYesFeature or working branch name.
repoYesRepository in format "owner/repo".
titleYesPull request title.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose one meaningful trait — the draft is not published without explicit user approval — but omits what happens to the draft (where it lives, whether it expires), what permissions are needed, and whether repeated calls create duplicates.

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?

Two short sentences, zero filler, with the action stated first and the critical safety constraint immediately after. Nothing could be removed without losing information.

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 five-parameter mutation-like tool with no annotations and no output schema, the definition covers the safety gate but not the return value (draft identifier, URL, or confirmation) or the approval workflow that follows. An agent knows what it does but not what it gets back or how to complete the flow.

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% and all five parameters are documented in the schema, so the description rightly does no parameter work. It adds no extra meaning such as head/base branch constraints or body formatting expectations, which is acceptable at this coverage level but not additive.

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+resource (draft a GitHub Pull Request proposal) in the first sentence, which is unambiguous. There is no competing PR tool among the siblings, so no differentiation statement is required, but the definition also doesn't name the relationship to github_search_issues or any publishing counterpart.

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 second sentence implies this is the safe, non-publishing path requiring explicit user approval, which hints at when to prefer it. However, it never states when to use this versus directly opening a PR, nor does it describe prerequisites such as existing branches or repo access.

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

All Exogram — Personal AI Agent & Workspace toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources