Skip to main content
Glama

Lifecycle Transition

lifecycle_transition
Destructive

Transitions an item through guarded lifecycle states—in_work, in_review, released, obsolete—rejects illegal state changes, and stamps/freezes the first revision on release.

Instructions

Move an item through the lifecycle state machine in_work -> in_review -> released -> obsolete, guarded by a transition table (#141 C2). An illegal edge (e.g. skipping review, or re-opening a released item in place) is rejected loudly; releasing stamps the item's first revision and freezes it.

registry: path to the items.json sidecar (written back on success). item: the item id to transition. to: the target lifecycle state. actor / note: optional provenance recorded in the item's transition log.

Returns {ok, state, rev}, or {ok:false, problems} on an illegal transition.

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": {
      "registry": "<registry>",
      "item": "<item>",
      "to": "<to>"
    },
    "name": "lifecycle_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
itemYes
noteNo
actorNo
registryYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Goes well past the annotations: it discloses that the items.json sidecar is written back on success, that releasing stamps the first revision and freezes the item, and that illegal edges fail loudly. That is exactly the kind of mutation detail an agent needs given destructiveHint=true. It does not mention any auth/permission requirements or concurrency behavior, so not a 5.

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-loads the state machine, then a compact parameter glossary, then the return shape — every block earns its place. The '(#141 C2)' tracker reference is inert noise for an agent and is the only real waste.

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?

With no output schema, the description compensates by stating the return shape ({ok, state, rev} / {ok:false, problems}) and describing the transition-log side effect. Missing only the current-state discovery path and any note on whether 'to' accepts values outside the four listed states.

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

Parameters4/5

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

Schema description coverage is only 17%, so the description must carry the load and largely does: it defines registry (path to the sidecar, written back), item (item id), to (target state), and actor/note (provenance for the transition log). The only gap is that 'to' is not stated as a closed set of values even though the four states are listed in the intro, and the workspace parameter is left to the schema.

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?

Names a specific verb+resource ('Move an item through the lifecycle state machine') and enumerates the exact state sequence in_work -> in_review -> released -> obsolete, so the operation is unmistakable. It does not explicitly contrast itself with the sibling lifecycle_editable / lifecycle_classify_change / lifecycle_apply_change tools, which keeps it off a 5.

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?

Gives negative conditions clearly ('an illegal edge, e.g. skipping review, or re-opening a released item, is rejected'), which implies when it is appropriate. However it never routes the agent to the sibling checks that would prevent a failed call (lifecycle_editable, lifecycle_classify_change), so the when-vs-alternative guidance is only implied.

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