mcp-gh-forge

Overview Schema Source Related Servers Discussions Admin

run_forge_macro

Execute automated Git and GitHub macros to consolidate changes, retrieve modified files, draft and save, or manage branches with a single command.

Instructions

Executes powerful multi-step local Git and cloud GitHub automated scripts (consolidate, get-changed-files, draft-and-save, branch-init, branch-cleanup).

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": {
      "action": "<action>",
      "argument": "<argument>"
    },
    "name": "run_forge_macro"
  }
}

Input Schema

Name	Required	Description	Default
`action`	Yes	The targeted script action block to execute.
`argument`	Yes	The parameter required by the action (e.g., Issue title, PR number, commit revision hash).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 17, 2026

TDQS

B3.3/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. It describes the tool as 'powerful multi-step' but does not disclose potential side effects (e.g., destructive operations like 'branch-cleanup'), required permissions, or behavioral details beyond the action names. This is insufficient for a script execution tool.

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?

The description is a single sentence that efficiently conveys the tool's purpose and lists all actions. It is front-loaded with the verb and resource. Slightly longer descriptions could add more details without being verbose, but it is concise enough.

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?

No output schema is present, and the description does not mention return values, error behaviors, or post-execution state. For a multi-step automation tool, this leaves significant gaps for the agent. The description is incomplete for safe and correct invocation.

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 coverage is 100% with both parameters having descriptions in the schema. The tool description adds the list of enum values but does not explain each action's purpose or the argument format beyond what the schema provides. Baseline 3 is appropriate.

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 uses specific verb 'executes' and identifies the resource as 'multi-step local Git and cloud GitHub automated scripts'. It lists all five script actions, making the tool's function clear and distinguishing it from potential siblings (though none exist).

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 lists the available actions but provides no guidance on when to use each action or when to choose this tool over alternatives. No explicit usage context, when-not, or alternative tools are mentioned.

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

Deploy Server

Other Tools

run_forge_macroB