Skip to content

fix: CloudBase MCP 缺少云函数调用测试工具和可用日志，导致部署后无法验证功能正确性 #565

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
binggg wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: CloudBase MCP 缺少云函数调用测试工具和可用日志，导致部署后无法验证功能正确性 #565

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions config/source/skills/cloud-functions/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,12 +101,18 @@ Use this skill when developing, deploying, and operating CloudBase cloud functio
- Keep `functionRootPath` as the parent directory of the function folder
- Use CLI only as a fallback when MCP tools are unavailable

4. **Prefer doc-first fallbacks**
4. **Verify the deployed function before concluding**
- For Event Functions, use `manageFunctions(action="invokeFunction")` with a realistic payload instead of assuming deployment success means runtime correctness
- Capture any returned request or invocation identifier and follow with `queryFunctions(action="listFunctionLogs")` or `queryFunctions(action="getFunctionLogDetail")` when the function output is empty, unexpected, or throws
- If direct function logs are insufficient, first check `queryLogs(action="checkLogService")`, then search CLS with `queryLogs(action="searchLogs")`
- In completion notes, state what was invoked, whether the invocation succeeded, and which logs were checked

5. **Prefer doc-first fallbacks**
- If a task falls back to `callCloudApi`, first check the official docs or knowledge-base entry for that action
- Confirm the exact action name and parameter contract before calling it
- Do not guess raw cloud API payloads from memory

5. **Read the right detailed reference**
6. **Read the right detailed reference**
- Event Function details -> `./references/event-functions.md`
- HTTP Function details -> `./references/http-functions.md`
- Logs, gateway, env vars, and legacy mappings -> `./references/operations-and-config.md`
Expand Down
Loading