fix: callCloudApi MCP 工具的 schema/prompt 未清晰标注 CreateUser 必填参数（EnvId），且参数命名约定不明确导致模型首次调用失败

[binggg]

Attribution issue

• issueId: issue_mojd35i1_ptw5mr
• category: tool
• canonicalTitle: callCloudApi MCP 工具的 schema/prompt 未清晰标注 CreateUser 必填参数（EnvId），且参数命名约定不明确导致模型首次调用失败
• representativeRun: atomic-js-cloudbase-cli-user-create/2026-04-29T01-10-03-cz94u1

Automation summary

• root_cause: The callCloudApi MCP tool's schema/description had two gaps: (1) it said "某些 Action 需要携带 EnvId" which was too vague — in reality 22/32 tcb actions require EnvId as a mandatory parameter, causing models to omit it on first call; (2) it didn't clarify that params must be flat key-value pairs matching official API field names (e.g., Name not UserName, Type not UserType, UserStatus not Status), and didn't warn against nesting params in sub-objects like { "User": {...} }. The agent's first call used { "User": { "UserName": "eval***user", "UserType": "internalUser", "Status": "ACTIVE" } } — wrong nesting AND wrong field names.
• changes: Modified mcp/src/tools/capi.ts with two layers of fixes:
• Layer 1 (description): Enhanced the tool's description and params description to (a) state that tcb 绝大多数 Action require EnvId as mandatory, (b) clarify params must be flat key-value pairs, not nested sub-objects, (c) add a CreateUser example with correct flat structure and field names (Name, Type, UserStatus), and (d) explicitly call out the common naming mistakes (Name vs UserName, Type vs UserType, UserStatus vs Status).
• **La

Changed files

• mcp/src/tools/capi.ts

[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-29T01:58:51.677Z

Cases

• [FAILED] — primary — evaluation failed