Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Read branch publication

stack_publish_status
Read-onlyIdempotent

Read a published branch’s status: absent, pushed, opened, or registered, plus head commit, PR, and Auto patch/land state. It changes nothing; rerun publishing after a lost response.

Instructions

Read how far a branch published with stack_publish got: absent, pushed (branch on GitHub, no pull request), opened (pull request open, stack not registered) or registered, with the head commit and tree on GitHub, the pull request and the stack's Auto patch and Auto land state. Changes nothing. Call it after a lost stack_publish response, then call stack_publish again to resume.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stack_publish_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNo
repoNo
ownerNo
branchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so "Changes nothing" is mostly redundant, but the description goes further by describing what the read returns: head commit and tree on GitHub, the pull request, and Auto patch/Auto land state. With no output schema, that payload disclosure is genuinely valuable. It stops short of noting cost, latency, or behavior when the branch was never 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?

Front-loaded with the core action, then the state enumeration, then the recovery instruction. It is dense but every clause carries information; the only wasted phrase is "Changes nothing", which the annotations already state.

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?

The absence of an output schema is well compensated by the enumerated states and returned artifacts, and the recovery guidance is complete. However, a four-parameter tool with zero schema documentation leaves the agent guessing how to scope the call (which of cwd/repo/owner/branch are needed), which is a real gap for this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description carries the full burden and largely fails: only "branch" is implicitly addressed via "a branch published with stack_publish". It never explains cwd, repo, or owner, nor what happens when they are omitted (all parameters are optional).

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?

States a specific verb and resource ("Read how far a branch published with stack_publish got") and enumerates the exact outcome space: absent, pushed, opened, registered. That enumeration lets an agent distinguish this from stack_status or stack_publish without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ("after a lost stack_publish response") and the follow-up action ("then call stack_publish again to resume"), which is exactly the when-to-use routing an agent needs. The recovery workflow is unambiguous.

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