Skip to main content
Glama

Lifecycle Apply Change

lifecycle_apply_change
Destructive

Apply a sanctioned change to a released item: preserve F3 to open a new revision on the same part, or break F3 to allocate a new part with a supersedes link.

Instructions

Apply a change to a RELEASED item, dispatching on the F3 predicate (#141 C2) — the sanctioned way to change a frozen part. An F3-preserving change opens a new revision on the SAME part number (rev A->B, back to in_work); an F3-breaking change allocates a NEW part number as a new item (new_item required) carrying a supersedes back-link, leaving the released item untouched.

registry: path to the items.json sidecar (written back on success). item: the released item id being changed. after: the proposed new metadata (attribute object). new_item: id for the new item when the change is F3-breaking. extra_f3 / actor / note: optional, as in lifecycle_classify_change / lifecycle_transition.

Returns {ok, disposition, item, part_number, rev, ...}, or {ok:false, problems} (e.g. the item is not released, or an F3-break lacks new_item).

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>",
      "after": "<after>"
    },
    "name": "lifecycle_apply_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
noteNo
actorNo
afterYes
extra_f3No
new_itemNo
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

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds what is actually mutated: the registry sidecar is written back on success, a released part gets a new revision and returns to in_work, an F3-break leaves the original released item untouched and creates a supersedes back-link. It also discloses failure modes ('not released', 'F3-break lacks new_item'). Nothing here contradicts the annotations.

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: the core semantic model comes first, then a compact parameter glossary, then return/error shapes — a sensible order with little filler. Minor cost from the opaque issue reference '(#141 C2)' and the wrapped em-dash clause, which add characters without adding agent-relevant meaning.

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?

Eight parameters, a nested object, destructive semantics and no output schema — the description covers all of it, including the return shape ({ok, disposition, item, part_number, rev} and the {ok:false, problems} failure form). An agent has everything needed to invoke it and interpret the result.

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 coverage is only 13% (just the workspace field), so the description must compensate and largely does: registry, item, after, and new_item each get a one-line semantic gloss, and extra_f3/actor/note are defined by reference to the sibling tools. Two gaps remain — `after` is described only as 'the proposed new metadata (attribute object)' with no shape guidance, and the `workspace` parameter is never mentioned, though its schema description covers it.

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?

Specific verb+resource+scope: 'Apply a change to a RELEASED item, dispatching on the F3 predicate'. It explicitly distinguishes itself from lifecycle_classify_change and lifecycle_transition, naming them for the optional parameters, and states the sanctioned-change framing that separates it from generic mutation 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?

The two branches are spelled out with the precondition that selects each: F3-preserving opens a new revision, F3-breaking requires new_item and allocates a new part. This effectively tells the agent which path to take. It stops short of explicitly saying 'run lifecycle_classify_change first' or listing when NOT to call it, so it is strong context rather than a full routing rule.

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