Skip to main content
Glama

Assembly Lock

assembly_lock
Destructive

Records component hashes and mate dependencies in a lockfile to establish a provenance baseline, helping coordinators detect drift across a team after a clean merge.

Instructions

Write a lockfile recording each component's content hash, published- interface hash, and mate dependencies — the provenance baseline a coordinator uses to detect drift across a team. Call after a clean merge. lockfile defaults to .lock.json. Returns {lockfile, components}.

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": {
      "manifest": "<manifest>"
    },
    "name": "assembly_lock"
  }
}

Input Schema

NameRequiredDescriptionDefault
lockfileNo
manifestYes
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 destructiveHint=true and openWorldHint=false; the description adds value by stating exactly what gets recorded, the default output path, and the return keys. It does not say whether an existing lockfile is overwritten, which matters given the destructive hint.

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?

Front-loaded with the write action and its payload, then the timing cue, the default, and the return shape. No sentence is redundant.

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 usefully states 'Returns {lockfile, components}', and the purpose/precondition/default path are all covered. The one missing piece is overwrite/conflict behavior for a tool flagged destructive.

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 33% (only workspace is documented), so the description must compensate — and it does for lockfile by giving the default filename pattern '<manifest>.lock.json'. The manifest parameter's role is only implied by the surrounding sentence.

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?

Specific verb plus resource: writes a lockfile recording content hashes, published-interface hashes and mate dependencies. The 'provenance baseline ... to detect drift' framing implicitly separates it from assembly_lock_check, but no sibling is named explicitly.

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?

'Call after a clean merge' gives a concrete precondition for invocation. It stops short of naming alternatives (assembly_lock_check for verification, baseline_create for project baselines) or stating when not to re-lock.

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