fix: validate required SDK tool arguments before execution

[HarshMN2345]

Missing required arguments to hidden SDK tools now produce a client-input error naming the missing fields before SDK execution. For example, calling functions_create_variable without variable_id previously raised an internal TypeError, even though the generated tool schema already marked that field required.

Validate the existing schema's required keys after argument alias normalization. Supplied IDs and empty values remain unchanged, and optional SDK defaults still apply. No resource IDs are generated implicitly.

Fixes MCP-A.

Validation:

• Reproduced the reported missing-argument TypeError against the locked SDK. The public-handler regression fails without validation and passes with the fix.
• Tests exercise the public MCP call handler with real catalog metadata and a fake SDK service boundary. They assert returned input errors and successful results preserving supplied IDs, empty values, camelCase aliases, and omitted optional fields.
• Python 3.12: 257 unit tests passed; Ruff, Black, Pyright, and Docker build passed.
• Integration discovery: 10 passed, 14 skipped because Appwrite credentials were not configured.

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge, with no outstanding correctness, security, or repository-rule violations.

Summary

• Reports all missing required fields deterministically.
• Preserves supplied IDs, camelCase aliases, empty values, and omitted optional arguments.
• Reworks regression coverage through the public MCP tool-call handler.

_{Reviews (2) · Last reviewed commit: "test: cover required arguments through p..."}