fix: MCP工具命名与发现性不足导致云函数创建任务未执行

[binggg]

Attribution issue

• issueId: issue_mo8z633l_qhka36
• category: tool
• canonicalTitle: MCP工具命名与发现性不足导致云函数创建任务未执行
• representativeRun: atomic-js-cloudbase-timer-trigger/2026-04-21T18-45-20-2tpbig

Automation summary

• root_cause: The MCP tool descriptions for queryFunctions and manageFunctions did not adequately emphasize trigger-related operations. When an agent needed to create a timer-triggered cloud function, the discoverability of the createFunctionTrigger action was insufficient because: (1) trigger operations were buried in general descriptions without specific keywords like "timer", (2) the action examples did not include trigger-related actions, and (3) the cron format requirements were not prominent in parameter descriptions.
• changes: Updated mcp/src/tools/functions.ts with improved tool descriptions:

1. Enhanced queryFunctions description to explicitly mention "触发器相关：使用 listFunctionTriggers 查询函数的定时触发器（timer）配置"
2. Added listFunctionTriggers to the action examples in the action parameter description
3. Enhanced manageFunctions description to explicitly mention timer trigger operations: "管理触发器（timer定时触发器）" and "定时触发器：使用 createFunctionTrigger 创建 timer 触发器（支持7段cron表达式），deleteFunctionTrigger 删除触发器"
4. Added createFunctionTrigger and deleteFunctionTrigger to the action examples
5. Enhanced the triggers parameter description to include cron format information: "timer

Changed files

• mcp/package-lock.json
• mcp/package.json
• 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: PASSED
• summary: all planned evaluation cases passed
• updated_at: 2026-04-28T14:44:52.606Z

Cases

• [PASSED] — primary — evaluation passed

[binggg]

代码冲突了