Skip to main content
Glama

dev_cycle_run

Run the end-to-end development loop: commit changes, trigger CI, wait for results, and summarize outcomes.

Instructions

Run the end-to-end development loop — commit, trigger CI, wait for results, return a summary — in a single aggregated call. Internally it: (1) commits and pushes the working tree via "lgh up" (requires the LGH daemon running), (2) waits for the ActionD CI/CD jobs triggered by that push, and (3) collects every job result into one structured output. Requires a message (the commit text); optional path (repo directory, defaults to the MCP client's working directory), timeout in seconds (default 300), profile (fast/full/release — switched temporarily for this run and restored afterwards; omit to keep the current profile), and auto_rollback (default false; on failure, resets the repo to the pre-push commit). Use it after editing code to commit, test, and verify in one step; the result reports success, the commit sha, per-job statuses with durations, artifacts, rollback info when applicable, and a human-readable summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoRepository path (defaults to the MCP client's working directory)
messageYesGit commit message
profileNoExecution profile for this run: fast/full/release (default: keep the current setting) - fast: minimal CI, core lint and test only - full: complete CI, adds security scan, coverage, etc. - release: full CI/CD, adds build and deploy
timeoutNoWait timeout in seconds (default 300 = 5 minutes)
auto_rollbackNoOn failure, automatically roll back to the previous commit (default false)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv0.1.1
    • changedInput schema / properties / auto_rollback / description
      Previous value: -"失败时自动回滚到上一个 commit(默认 false)"New value: +"On failure, automatically roll back to the previous commit (default false)"
    • changedInput schema / properties / message / description
      Previous value: -"提交信息"New value: +"Git commit message"
    • changedInput schema / properties / path / description
      Previous value: -"仓库路径(默认当前目录)"New value: +"Repository path (defaults to the MCP client's working directory)"
    • changedInput schema / properties / profile / description
      Previous value: -"执行 profile:fast/full/release(默认不切换,保持当前设置)\n- fast: 最小 CI,只跑核心 lint 和 test\n- full: 完整 CI,加上安全扫描、覆盖率等\n- release: 完整 CI/CD,加上 build 和 deploy"New value: +"Execution profile for this run: fast/full/release (default: keep the current setting)\n- fast: minimal CI, core lint and test only\n- full: complete CI, adds security scan, coverage, etc.\n- release: full CI/CD, adds build and deploy"
    • addedInput schema / properties / profile / enum
      Added value: +[
      +  "fast",
      +  "full",
      +  "release"
      +]
    • changedInput schema / properties / timeout / description
      Previous value: -"等待超时秒数(默认 300 = 5分钟)"New value: +"Wait timeout in seconds (default 300 = 5 minutes)"
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

The description discloses the internal sequence (commit/push, wait, collect), the LGH daemon prerequisite, temporary profile switching, and the optional auto-rollback behavior, so an agent can anticipate side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the numbered internals help structure, but the later parameter summary largely repeats the input schema, making the description longer than necessary.

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

Completeness5/5

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

With no output schema, the description compensates by listing the result contents (success, commit sha, per-job statuses with durations, artifacts, rollback info, and a human-readable summary) as well as prerequisites and defaults.

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% and every parameter already has a description, so this is at the baseline; the prose restates the schema fields without adding substantial new semantic detail.

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 opens with a specific verb and resource ('Run the end-to-end development loop') and explains that it aggregates commit, CI trigger, wait, and summary into one call, making it easy to distinguish from the individual actiond_* sibling tools.

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

Usage Guidelines4/5

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

It gives an explicit usage cue ('Use it after editing code to commit, test, and verify in one step') and highlights the aggregation, though it does not explicitly name alternatives or state when not to use it beyond the single-call framing.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JoeGlenn1213/ActionD'

If you have feedback or need assistance with the MCP directory API, please join our Discord server