@4da/mcp-server

Official

by 4DA-Systems

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Upgrade planner

upgrade_planner

Read-only

Generate a prioritized upgrade plan for a project's dependencies, showing per-package targets, lockfile fixes, and minimum versions that resolve vulnerabilities.

Instructions

Prioritized upgrade plan for one project (project_path): the 4DA app's work order when computed (per-line targets, manifest vs lockfile fix), else the smallest version that fixes each vulnerability. Call when the user asks what to upgrade.

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": "upgrade_planner"
  }
}

Input Schema

Name	Required	Description
`package`	No	Plan for this one package only (exact name, any ecosystem). Default: every dependency.
`include_dev`	No	Dev-only packages (labelled isDev). Default (unset): vulnerable devDependencies and dev-only transitive packages are planned, as in vulnerability_scan; true also checks every devDependency for newer releases and deprecation; false leaves dev-only packages out and the summary counts them.
`project_path`	No	Project directory to plan for: the app's plan is narrowed to the steps (and installed lines) that touch it; the standalone plan resolves that project's lockfiles. "*" for every project the app tracks. Default: the project the server was started in, when that directory is a project.
`risk_threshold`	No	Only show upgrades at or above this risk level. Default: all
`max_recommendations`	No	Max recommendations to return. Default: 20

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv6.0.4Oct 27, 2026

changedInput schema / properties / include_dev / description

Previous value: -"Include devDependencies. Default: false"New value: +"Dev-only packages (labelled isDev). Default (unset): vulnerable devDependencies and dev-only transitive packages are planned, as in vulnerability_scan; true also checks every devDependency for newer releases and deprecation; false leaves dev-only packages out and the summary counts them."

Changed1 schema field changedv6.0.2Oct 7, 2026

addedInput schema / properties / project_path

Added value: +{
+  "description": "Project directory to plan for: the app's plan is narrowed to the steps (and installed lines) that touch it; the standalone plan resolves that project's lockfiles. \"*\" for every project the app tracks. Default: the project the server was started in, when that directory is a project.",
+  "type": "string"
+}

First observedv6.0.1Oct 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuine behavioral context beyond that: it discloses that results depend on whether the work order has been computed, that lines carry per-line targets, and that manifest vs lockfile fixes are distinguished, with a smallest-version fallback. It does not mention ordering/tie-breaking details or truncation behavior beyond max_recommendations.

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 with the resource and the primary scoping parameter, followed by a single actionable trigger sentence. It is dense — the parenthetical about work order modes packs a lot in — but every clause carries information and nothing is padded.

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?

No output schema exists, but the description explains the two result shapes (prioritized work-order steps with per-line targets vs. minimal fixing versions), which is the key thing an agent needs. For a read-only, five-option tool this is close to complete; missing only guidance on how results are ordered or bounded.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so parameter meaning is already fully documented; the description largely restates project_path and the plan modes rather than adding new syntax or defaults. Baseline 3 applies when the schema carries the parameter burden, with marginal added framing here.

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?

States a specific verb+resource: 'Prioritized upgrade plan for one project'. It also describes the two output modes (computed 4DA app work order vs. smallest fixing version), which lets an agent know what it will get. It stops short of explicitly differentiating from upgrade_impact or vulnerability_scan in the main text — vulnerability_scan only appears inside the include_dev parameter description.

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 when the user asks what to upgrade' gives a clear positive trigger, and the include_dev/project_path parameters clarify scope conditions versus vulnerability_scan defaults. There is no explicit when-not to use it (e.g., versus upgrade_impact for impact analysis), so alternatives are only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server