Tool Reference¶
15 tools. Arguments marked (optional) have safe defaults. registry accepts
any of the supported registries (and their aliases).
Lookup¶
get_latest_version¶
Latest version of a package.
- package_name (string) — format depends on registry (e.g. groupId:artifactId for Maven, owner/repo for GitHub).
- registry (string)
get_package_info¶
Latest version plus description, homepage, and publish date when available.
- package_name (string), registry (string)
get_install_command¶
Ready-to-use install command for the package at its latest version.
- package_name (string), registry (string)
- dev (boolean, optional) — dev dependency (npm).
compare_versions¶
Semver comparison of a version you hold against the latest. Reports
update-available / up-to-date / ahead-of-latest.
- package_name (string), current_version (string), registry (string)
check_multiple_packages¶
Batch latest-version check; per-item success/error.
- packages (array of { package_name, registry })
Version reasoning (no network for the pure-semver tools)¶
check_compatibility¶
Does version satisfy each given constraint?
- package_name (string), version (string)
- dependencies (array of { name, constraint })
detect_conflicts¶
Find packages required at incompatible versions.
- dependencies (array of { name, constraint, source? })
find_compatible_version¶
Highest published version satisfying all constraints.
- package_name (string), registry (string)
- constraints (array of { name, constraint })
suggest_upgrade_path¶
Step-by-step path from current to target (defaults to latest), stepping through
intermediate majors, with risk and breaking-change notes.
- package_name (string), registry (string), current_version (string)
- target_version (string, optional), dependencies (array, optional)
Project tools¶
scan_project¶
Inventory every dependency manifest and lock file.
- project_path (string, absolute)
- include_lock_files (boolean, optional, default true)
- max_depth (number, optional, default 10)
check_outdated¶
Scan a project and check every dependency against its registry; reports
outdated packages with upgrade type and risk.
- project_path (string)
- include_dev (boolean, optional, default true)
- include_lock_files (boolean, optional, default true)
resolve_conflicts¶
Detect version conflicts in a project and suggest a compatible resolution per
package. Read-only.
- project_path (string)
- include_lock_files (optional), allow_downgrade (optional, default false), prefer_latest (optional, default true)
optimize_versions¶
Whole-project upgrade plan (per dependency: keep / upgrade / downgrade / remove,
with risk). Read-only. Feed the result to validate_upgrade_plan / apply_upgrades.
- project_path (string)
- include_lock_files (optional), allow_downgrade (optional), prefer_latest (optional)
validate_upgrade_plan¶
Check a plan for breaking (major) bumps, circular dependencies, and constraint
violations before applying. Read-only.
- project_path (string)
- plan (array of plan items, as from optimize_versions)
- allow_major_version_changes (optional, default true), strict_mode (optional, default false)
apply_upgrades¶
Apply a plan to the project's manifests (package.json, requirements.txt,
Cargo.toml, go.mod, pom.xml, ...).
- project_path (string)
- plan (array of plan items)
- dry_run (boolean, optional, default true — pass false to write)
- create_backup (boolean, optional, default true)
A plan item is: { package, registry, currentVersion?, currentConstraint?,
suggestedVersion, suggestedConstraint?, action, reason?, risk?, affectedFiles }
where action is one of keep | upgrade | downgrade | remove and
affectedFiles are paths relative to project_path.