fix: CloudBase MCP 工具参数设计不清晰且错误提示不具体

[binggg]

Attribution issue

• issueId: issue_mo8yrp43_f3zmbp
• category: tool
• canonicalTitle: CloudBase MCP 工具参数设计不清晰且错误提示不具体
• representativeRun: atomic-js-cloudbase-function-detail/2026-04-21T18-34-27-iy1ret

Automation summary

**

• root_cause: The CloudBase MCP tools were returning generic "400 invalid parameter value" errors from the CloudBase API without specifying which parameter was wrong or what the correct format should be. This made it difficult for users to understand and fix parameter issues.
• changes:

1. Added buildFunctionQueryErrorMessage function (mcp/src/tools/functions.ts:439-511): A new exported helper function that detects generic API errors and provides specific parameter guidance based on the action type (getFunctionDetail, listFunctionLogs, etc.). It shows:

• Which parameters are required for the specific action
• The actual input parameters received for debugging
• Suggestions to use listFunctions when a function is not found

2. Enhanced getFunctionDetail error handling (mcp/src/tools/functions.ts:649-692): Wrapped the API call in try-catch to use the enhanced error messages. Also improved the validation error to include usage examples.
3. Improved tool parameter descriptions (mcp/src/tools/functions.ts:1606-1638): Enhanced the queryFunctions tool's action parameter description to list all available actions with their specific requirements, and clarifie

Changed files

• mcp/src/tools/functions.test.ts
• mcp/src/tools/functions.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-28T17:04:02.794Z

Cases

• [FAILED] — primary — evaluation failed