Skip to main content
Glama
Sign In
killbottleneck-mcp

killbottleneck-mcp

Official
by tengolabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

create_event

Create a calendar event with a time, place, participants and reminder, or book a shared room, resource or time-off slot. Overlapping bookings are refused and the next free slot is returned.

Instructions

Create a calendar EVENT with a time (meeting, call, dentist…) — NOT a task and not part of any map. Personal by default; calendar (a name from list_calendars) puts it into a SHARED calendar: company events (kind shared), a room/car booking (kind resource — needs time; end_time defaults to +60 min; an overlapping booking is refused and the error names the next free slot) or time off (kind absence — all-day, end_day for a range, participants = who is away, default the key owner). Optional participants (e-mails of instance members from list_people; each sees the event in their calendar) and a reminder N minutes before (in-app + e-mail). Times are the instance's local time.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "day": "<day>"
    },
    "name": "create_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesYYYY-MM-DD
noteNo
timeNoHH:MM (24h); omit for an all-day event
placeNowhere it takes place (room 214, address, pitch) — max 200 characters; a room to BOOK is a shared calendar instead
titleYes
end_dayNoYYYY-MM-DD; last day of a multi-day event (vacation)
calendarNoname or id of a shared calendar (list_calendars); omit for a personal event
end_timeNoHH:MM (24h); end of a timed event (room booking)
participantsNoe-mails of instance members
remind_before_minNoreminder N minutes before start (0 = at start); omit for no reminder

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full behavioral burden and does so well: end_time defaults to +60 min, overlapping resource bookings are refused with an error naming the next free slot, participants each see the event in their own calendar, reminders fire in-app plus e-mail, absence defaults to the key owner, and all times are instance-local. These are exactly the non-obvious consequences an agent needs before calling a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and the exclusion before any conditional detail, and every clause carries information (kinds, defaults, error behavior, time zone). It is a single very dense paragraph with stacked parentheticals that reward a careful read but are slightly harder to scan than a segmented structure would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter mutation tool with no annotations and no output schema, the description covers modes, defaults, failure behavior, and time semantics thoroughly. The remaining gap is the return value — there is no output schema, so the description could have said what comes back after creation (e.g., the created event or its id).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the baseline is 3; the description earns extra by explaining what the schema cannot — that `calendar` selects a kind (shared/resource/absence) rather than just a location, that `end_day` covers multi-day absences, that `participants` must be instance member e-mails, and that `end_time` has a computed default. It does not restate the day/time formats, which the schema already handles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb (create) plus resource (calendar EVENT) with concrete examples (meeting, call, dentist), and it actively rules out the nearest confusions — 'NOT a task and not part of any map' — which separates it from create_map/create_page siblings. An agent can classify the request correctly without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the default mode (personal) and the exact condition that changes behavior: supplying `calendar` from list_calendars moves it into a shared calendar, with the three resulting kinds spelled out. Prerequisites (list_calendars, list_people) are named. It stops short of explicit when-not-to-use guidance against update_event or the batch create_events sibling, so not a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools