wolfpack-mcp 1.0.17 → 1.0.18
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.js +6 -5
- package/package.json +1 -1
package/dist/index.js
CHANGED
|
@@ -258,12 +258,13 @@ class WolfpackMCPServer {
|
|
|
258
258
|
{
|
|
259
259
|
name: 'list_teams',
|
|
260
260
|
description: 'List all teams (projects) you have access to. ' +
|
|
261
|
+
'TERMINOLOGY: In this software, "team" and "project" are synonymous and interchangeable. All tool names and parameters use "team" (e.g., team_id), but the concepts are identical. ' +
|
|
261
262
|
'IMPORTANT - PROJECT FOCUS RULES: ' +
|
|
262
|
-
'1) Call this FIRST to identify which project you are working in. ' +
|
|
263
|
-
'2) Once you identify a
|
|
264
|
-
'3) NEVER perform bulk actions across multiple
|
|
265
|
-
'4) If the user mentions a specific project, use that
|
|
266
|
-
'5) If unclear which
|
|
263
|
+
'1) Call this FIRST to identify which team/project you are working in. ' +
|
|
264
|
+
'2) Once you identify a team, STAY WITHIN that team for all operations unless the user explicitly asks to switch. ' +
|
|
265
|
+
'3) NEVER perform bulk actions across multiple teams - always work in one team at a time. ' +
|
|
266
|
+
'4) If the user mentions a specific team or project, use that for all subsequent operations. ' +
|
|
267
|
+
'5) If unclear which team to use, ASK the user before proceeding. ' +
|
|
267
268
|
'Returns team IDs, slugs, and names. Single-team users have their team auto-selected; multi-team users must specify team_id in other tool calls.',
|
|
268
269
|
inputSchema: {
|
|
269
270
|
type: 'object',
|