fix: MCP 工具集无创建内部用户工具，Assistant 无从下手导致用户未创建

[binggg]

Attribution issue

• issueId: issue_moj1eq6r_gwt9rh
• category: tool
• canonicalTitle: MCP 工具集无创建内部用户工具，Assistant 无从下手导致用户未创建
• representativeRun: atomic-js-cloudbase-cli-user-create/2026-04-28T19-44-37-74be05

Automation summary

root_cause: The MCP managePermissions tool's createUser action only supported username, password, userStatus, and description fields. However, the CloudBase Manager SDK's createUser API supports many more fields including type (user type), nickName, phone, email, and avatarUrl. When the Assistant tried to create a user with the required fields (nickname, phone, email, user type), it couldn't because these parameters weren't exposed in the MCP tool schema.
changes: Updated mcp/src/tools/permissions.ts to:

1. Added new input schema fields: userType (enum: internalUser/externalUser), nickname, phone, email, avatarUrl
2. Added destructuring of these fields in the async handler
3. Passed these fields to both cloudbase.user.createUser() and cloudbase.user.modifyUser() calls
4. Mapped nickname parameter to SDK's nickName field (camelCase)
   validation:

• All 3 required skill/doc regression tests pass: build-skills-repo.test.js, build-compat-config.test.js, skill-quality-standards.test.js
• TypeScript compilation succeeds with no new errors
  follow_up: None. The Assistant will now be able to create internal users with all requi

Changed files

• mcp/src/tools/permissions.ts

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[binggg]

Attribution post-PR evaluation

• visibility: internal identifiers, run ids, and private links are intentionally omitted
• attempt: 1
• eval_scope: primary_only
• overall: FAILED
• summary: at least one planned evaluation case failed
• updated_at: 2026-04-28T20:18:11.826Z

Cases

• [FAILED] — primary — evaluation failed