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 tool managePermissions with action=createUser was missing critical parameters that the underlying CloudBase Manager SDK supports. The tool only exposed username, password, userStatus, and description, but the SDK supports additional fields: uid, type (internalUser/externalUser), nickName, phone, email, and avatarUrl. This caused the agent in the evaluation run to be unable to create users with phone, email, nickname, or userType fields, as these parameters weren't available in the tool schema.
• changes: Added missing parameters to mcp/src/tools/permissions.ts:

1. Added userType parameter (enum: internalUser | externalUser) to inputSchema
2. Added nickName parameter (string, 2-64 chars) to inputSchema
3. Added phone parameter (string, 11-digit CN mobile number) to inputSchema
4. Added email parameter (string, email format) to inputSchema
5. Added avatarUrl parameter (string, URL) to inputSchema
6. Updated TypeScript type definitions for the handler function
7. Passed all new parameters to the SDK calls for both createUser and updateUser actions
8. Added uid parameter pass-through for createUser (to sup

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:50:47.288Z

Cases

• [FAILED] — primary — evaluation failed