Skip to main content
Glama

Lifecycle Classify Change

lifecycle_classify_change
Read-only

Compare before/after attributes to decide whether a change needs a new part number or a revision bump based on Form/Fit/Function impact.

Instructions

The deterministic Form/Fit/Function predicate (#141 C2): compare an item's before/after attributes and decide rename-vs-revise. A change touching a Form/Fit/Function (public, interface-defining) attribute breaks interchangeability => "new_part_number" (allocate a new number); a change to only internal/hidden attributes is interchangeable => "revise" (bump the revision, same part number).

before / after: attribute objects (the item's interface-defining + internal attributes, before and after the proposed change). extra_f3: optional map of extra attribute name -> F3 leg ("form"/"fit"/ "function") for domain-specific interface attributes.

Returns the verdict {disposition, f3, changed, f3_changed, categories, reason} where disposition is "revise" / "new_part_number" / "noop".

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": {
      "before": "<before>",
      "after": "<after>"
    },
    "name": "lifecycle_classify_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterYes
beforeYes
extra_f3No
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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this by framing the tool as a 'deterministic predicate' — a pure computation with no side effects. It also lists the verdict fields returned, though it doesn't clarify the (apparently inert) workspace parameter or error behavior.

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?

The definition is front-loaded with the core predicate and the disposition rule before the parameter and return notes. It is dense but each block contributes; the parenthetical issue reference (#141 C2) is minor noise but not a distraction.

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 enumerating the verdict fields {disposition, f3, changed, f3_changed, categories, reason}. It is complete enough to call correctly, missing only edge-case semantics (e.g., what constitutes 'noop' or how missing attributes are treated).

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 25%, so the description must carry the load, and it does: 'before'/'after' are explained as attribute objects of interface-defining plus internal attributes, and 'extra_f3' is defined as a name -> F3 leg ('form'/'fit'/'function') map for domain-specific attributes. Only the workspace parameter is left to its schema description.

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 names a specific verb+resource with a precise semantic: comparing before/after attributes to decide rename-vs-revise via a Form/Fit/Function predicate. It even defines the two possible dispositions and their consequences, so an agent can distinguish this classification tool from mutating siblings like lifecycle_apply_change or lifecycle_transition.

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?

The description explains the decision logic in detail (F3 change => new_part_number, internal-only => revise), which implies when this tool is appropriate. However, it never explicitly says when to call this versus siblings such as change_impact, lifecycle_transition, or lifecycle_editable, leaving the routing decision to inference.

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