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

SUMMARY:

• root_cause: The callCloudApi tool's schema/prompt did not clearly indicate the correct parameter naming for CreateUser. The agent used incorrect parameter names (UserName, UserType, Status) instead of the correct API parameter names (Name, Type, UserStatus). The tool description lacked a concrete example for CreateUser and did not explicitly warn about the specific naming convention, leading to first-call failures.
• changes: Made two changes to mcp/src/tools/capi.ts:

1. Updated the params schema description (line 211): Added a complete CreateUser example showing the correct parameter names (Name, Type, UserStatus) and explicitly noted the common naming mistakes to avoid (UserName vs Name, UserType vs Type, Status vs UserStatus). Also emphasized that parameter keys must exactly match the API definition (case-sensitive).
2. Added specific error guidance for CreateUser (lines 148-151): When a parameter error occurs for CreateUser, the error message now explicitly warns the user to use Name (not UserName), Type (not UserType), and UserStatus (not Status).

• validation: Successfully built the MCP package with `n

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-29T03:01:29.283Z

Cases

• [FAILED] — primary — evaluation failed