Built-in Support-Ticket helpers in the MCP server

[bradtaylorsf]

(replaces today’s prompt-based, error-prone workflow)

Helper	Purpose	Key details
validateUserCanSubmitTicket	Checks if the email belongs to a Salesforce contact who may open cases	– Takes an email → hits custom customer endpoint for account validation → returns accountId, contactId.– Returns null set if no matching account (user cannot submit).
createCase	Submits the Case object	– Consumes the accountId & contactId from the first helper.– Automatically describes the Case object, gathers required fields, injects IDs, then creates the record.– Handles errors deterministically; no prompt hacking.

Additional notes
• Both helpers are added to the forked Salesforce MCP; they should be generic enough for any org that uses the standard Case object.
• The “describe-first-then-submit” logic removes repeated prompt steps and prevents missing required fields.