MCP server for sending SMS through EngageLab
Single tool 'send_sms' has a basic schema with two string parameters (phone_number, message) and minimal descriptions. The tool description is adequate (58 chars) but parameter descriptions are generic and lack validation guidance. No output schema documented. No error handling guidance. No idempotency or retry semantics specified for a WRITE operation. Naming is clear (verb_noun pattern), but the implementation lacks production-grade rigor expected for a tool that performs irreversible side effects (sending SMS).
Send an SMS message through EngageLab
No output schema documented. Callers cannot know what the tool returns (success confirmation, message ID, timestamp, etc.), forcing LLMs to guess or make assumptions.
Parameter descriptions lack validation constraints. 'phone_number' does not specify format (E.164, digits-only, country code required?). 'message' lacks length limits or character restrictions. LLMs will pass invalid input without guidance.
No error handling guidance. Tool description does not explain what happens on failure (invalid number, rate limit, service outage). LLMs cannot determine if errors are retryable or user-fixable.
WRITE operation lacks idempotency semantics. No mention of idempotent keys, deduplication, or retry safety. Agents retrying on ambiguous failures risk sending duplicate SMS messages.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | 2026-07-28+ | v2 |
No confirmation or dry-run pattern for irreversible operation. Sending SMS cannot be undone, tool should support a preview or confirmation step to prevent accidental bulk sends.