Loading ToolBench

Reading the current corpus…

mcp-ical MCP server · D · ToolBench

mcp-ical

MCP server with 5 ICS / iCalendar tools. Generate events, build multi-event calendars, parse existing ICS, plus one-click 'Add to Google/Outlook Calendar' URLs. Free, MIT.

2026-07-28+STDIO5 tools

56/100

Definition Quality73

Protocol Readiness50

Supportability31

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

mcp-ical has well-structured tool definitions with complete input schemas and clear descriptions. All 5 tools follow verb_noun naming (create_event, parse_ics, google_calendar_url). Schemas are properly typed with required fields. However, parameter descriptions are sparse or missing for many fields (e.g., 'location', 'description', 'url' in create_event lack descriptions). Output schemas are not documented, callers cannot see what fields to expect from responses. Error handling is minimal; no recovery guidance or validation messages. The server lacks tool annotations (readOnlyHint, destructiveHint) despite all tools being read-only operations.

Tools (5)

create_calendarread onlysource verified73/100

Build a multi-event ICS calendar file from an array of events.

create_eventread onlysource verified75/100

Generate an RFC 5545 ICS file for a single calendar event.

google_calendar_urlread onlysource verified73/100

Build a one-click 'Add to Google Calendar' URL for an event (no auth needed).

outlook_calendar_urlread onlysource verified73/100

Build a one-click 'Add to Outlook Web Calendar' URL.

parse_icsread onlysource verified73/100

Parse an ICS file content and return an array of event objects.

Issues (5)

HIGHtool ↗

Output schemas not documented. Callers cannot see what fields create_event, create_calendar, parse_ics return. LLMs cannot plan downstream operations or extract required data.

create_eventcreate_calendarparse_icsgoogle_calendar_urloutlook_calendar_url

HIGHtool-description ↗

Many parameters lack descriptions. 'location', 'description', 'url', 'organizer_email', 'attendees' in create_event have no descriptions. LLMs cannot infer when to use these optional fields.

create_eventcreate_calendargoogle_calendar_urloutlook_calendar_url

MEDIUMtool ↗

No tool annotations. All 5 tools are read-only (generate ICS, parse, build URLs) but lack readOnlyHint annotation. Agents cannot distinguish safe tools from destructive ones.

create_eventcreate_calendarparse_icsgoogle_calendar_urloutlook_calendar_url

Recommendations

Document output schemas for all tools. E.g., create_event returns {ics: string, byte_length: number}. parse_ics returns {events: [{title, start, end, location, description, all_day}]}. This enables LLMs to chain operations.
Add descriptions to all parameters. E.g., 'location: Physical location or venue name for the event' and 'all_day: If true, treat start/end as dates only (YYYY-MM-DD), omitting time. Useful for all-day events like birthdays or holidays.'
Add readOnlyHint annotation to all 5 tools in the tool definition. This signals to agents that these tools are safe to call without side effects.
Improve error messages with actionable guidance. E.g., 'Invalid datetime: "2026-06-15". Expected ISO 8601 format: "2026-06-15T14:00:00Z" or "2026-06-15T14:00:00+02:00".'
Add parameter constraints. E.g., 'start and end must be valid ISO 8601 datetimes. If all_day is true, use YYYY-MM-DD format (e.g., "2026-06-15").' This prevents invalid input from LLMs.

Score history

Overall score trend

First recorded score · v2 rubric

56/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	56	2026-07-28+	v2