EnkAI has 3 tools with complete input schemas and descriptions. Tool naming follows verb_noun convention (createEventPage, getCalendarInfoForMonth, getCurrentISODate). Descriptions are present and reasonably detailed (194 - 250 chars, within baseline 34 - 392 range). However, output schemas are not documented, responses are returned as plain text wrapped in MCP content blocks rather than structured objects. Error handling exists but lacks recovery guidance (e.g., 'Failed to create event' does not suggest next steps). The createEventPage tool has a complex nested schema with proper Zod validation, but parameter descriptions could be more explicit about constraints (e.g., ISO8601 format is mentioned but not validated client-side). Prompts feature is implemented but adds minimal value, it delegates the real work back to the LLM.
Create an event and return the URL (admin page) for the event page. This page can be used to coordinate schedules and confirm attendance for events such as drinking parties, company events, outdoor activities, and trips. The generated URL has an expiration date, so please encourage the user to open and verify it promptly. After opening, the user should share it with others. When the URL is opened, there is a sharing feature that prompts participants to fill in their attendance.
Returns a map of dates to their English day names for a given month and year. Useful for event scheduling.
Returns the current date in ISO8601 format. Useful for event scheduling.
Output schemas not documented. Tools return plain text in MCP content blocks rather than structured objects with typed fields. LLMs cannot plan downstream calls or extract specific data (e.g., event ID, URL, calendar map structure).
Error messages lack recovery guidance. 'Failed to create event (status: 400)' does not tell the LLM what to do next. Should include: 'Invalid title length. Must be 1 - 50 characters.' or 'API error. Retry with different options or contact support.'
createEventPage description does not explicitly state it modifies state (creates an event). Agents need to know this is irreversible and should not be retried blindly on transient failures.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2026-07-28+ | v2 |
Parameter 'startAt' in createEventPage accepts ISO8601 strings but does not validate format client-side. Description mentions examples but does not enforce pattern. LLMs may pass invalid dates like '2025-13-45T25:00:00Z'.
Prompt 'createEventPage' delegates scheduling logic back to the LLM rather than providing structured guidance. It does not call getCalendarInfoForMonth or getCurrentISODate to help the LLM reason about dates, forcing the LLM to invent candidate dates.