Skip to main content
Glama
bernatch22

taskops

by bernatch22
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

taskops_merge

Integrate completed board cards into their milestone branch using no-fast-forward merges, stopping at the first failure to report per card; re-run to continue from the last success.

Instructions

Integrate DONE cards into their milestone branch (--no-ff, in the integration worktree): task= one, tasks=[…] those in order, done=true every card waiting under MERGE. A batch stops at the first failure, reports per card, and continues on a re-run. A conflict aborts clean. main is never touched. Orchestrator only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doneNointegrate every card the board groups under MERGE (done, not integrated), in that group's order. Re-run it after a stop: it continues where it left off.
noteNowith milestone= criteria_met=false: REQUIRED — which criteria are unmet and why landing is still right. It lands on the record beside the answer.
taskNoa DONE card → into its milestone branch
actorNowho is speaking, when it is not the session's own identity. Sub-agents share the session's ONE MCP server, so a spawned worker MUST pass the agent:<dev>/<name> its brief names on EVERY taskops call — without it the board hears the orchestrator.
tasksNointegrate exactly these DONE cards, in the order given — each through the same single-card path. Stops at the first failure and reports per card.
milestoneNoms-… → land the WHOLE milestone into the trunk. Refused while any card of it is open or unintegrated. The human's call — never do this with raw git in the shared checkout; the board must record the landing.
repo_pathNoanother project's board, by any path inside it. Default: the board this server started in. The host runs ONE MCP server per session, pinned to the directory it opened, so without this a second project is unreachable and the work leaves through curl instead of the tools.
criteria_metNowith milestone=: the human's answer to its criteria — recorded, never judged. true, or false with note= saying which are unmet and why landing is still right (a criterion that can only be checked after the trunk moves). Omitted, a chapter with criteria is refused and shown them.

Schema Changelog

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

  1. Changed2 schema fields changedv0.4.2
    • changedInput schema / properties / criteria_met / description
      Previous value: -"with milestone=: the human's answer to its criteria — recorded, never judged"New value: +"with milestone=: the human's answer to its criteria — recorded, never judged. true, or false with note= saying which are unmet and why landing is still right (a criterion that can only be checked after the trunk moves). Omitted, a chapter with criteria is refused and shown them."
    • addedInput schema / properties / note
      Added value: +{
+  "description": "with milestone= criteria_met=false: REQUIRED — which criteria are unmet and why landing is still right. It lands on the record beside the answer.",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

There are no annotations, so the description carries the full disclosure burden. It states the failure semantics (a batch stops at the first failure, reports per card, and continues on re-run), describes conflict behavior, and asserts a strong safety guarantee ('main is never touched').

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 definition is compact and information-dense, with five short sentences, each adding a new behavioral or imperative detail. Nothing is filler, and the primary action is front-loaded in the first sentence.

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 an 8-parameter mutating tool with no output schema, the description covers the main invocation modes, failure behavior, retry semantics, and a key safety property. It does not describe the return/report format in detail, but it names 'reports per card' and the schema covers the remaining conditions like milestone and criteria_met.

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 scoring baseline is 3. The coverage provides useful grouping of the modes, but most parameter-level semantics are already in the schema; the description adds little new meaning beyond that.

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 opening sentence names a precise action and resource: integrate DONE cards into their milestone branch, and adds technical specificity with --no-ff and the integration worktree. This clearly distinguishes the tool from the other taskops siblings such as taskops_update or taskops_comment.

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?

The description gives concrete invocation modes (one task, ordered tasks, all cards under MERGE), plus how a stopped batch should be re-run. It also restricts use to the 'orchestrator only', but does not explicitly compare against alternative tool names or name when not to use the tool, so it stops just short of top-level guidance.

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

Install Server

Other Tools

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/bernatch22/taskops'

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