Pending changesets (structured)
liquibase_statusLists pending Liquibase changesets for a target database and returns structured JSON showing up-to-date status or unapplied changes, so agents can verify migration state.
Instructions
List Liquibase changesets not yet applied to the target database, as structured JSON. Reports up-to-date vs a pending list. liquibase is on PATH — no mise/wrapper needed.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "liquibase_status"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cwd | No | Directory to run liquibase in (where the defaults file / changelog live). | |
| labels | No | Label expression to filter changesets (--labels). | |
| contexts | No | Context expression to filter changesets (--contexts). | |
| extraArgs | No | Additional raw arguments appended to the liquibase invocation. | |
| defaultsFile | No | Path to the Liquibase defaults file (--defaults-file), e.g. db-dev.properties. Usually carries the JDBC URL, credentials, and changelog path. | |
| changelogFile | No | Changelog path (--changelog-file); usually set in the defaults file instead. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pending | Yes | ||
| retained | No | ||
| upToDate | Yes | ||
| pendingCount | Yes |