Skip to main content
Glama
Sign In
killbottleneck-mcp

killbottleneck-mcp

Official
by tengolabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

list_events

Retrieve calendar events visible to the key owner—own, invited, and shared—within a date range, optionally filtered to one shared calendar. Read-only, includes multi-day events that overlap the range.

Instructions

List the calendar events the key owner sees — own, invited, and every event of the shared calendars — in a day range; default today−365 … +730. A multi-day event counts when it overlaps the range. Optional calendar = only that shared calendar. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoYYYY-MM-DD
fromNoYYYY-MM-DD
calendarNoname or id of a shared calendar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and covers a lot: the safety profile ("Read-only."), the visibility scope, the default range, the overlap rule for multi-day events, and the filtering effect of the calendar parameter. It stops short of disclosing pagination limits, response shape, or what happens with an unknown calendar name.

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

Conciseness5/5

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

One front-loaded sentence carries the purpose, scope, defaults, and filtering semantics with no filler. The em-dash clauses keep related facts grouped rather than padding length.

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 three-optional-parameter read tool with no output schema, the description covers scope, defaults, and filter behavior adequately. The remaining gap is what an event record contains and how results are bounded, which matters since there is no output schema to fall back on.

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

Parameters3/5

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

Schema description coverage is 100% (each of from/to/calendar has a format description), so the schema baseline of 3 applies. The description does add genuinely useful meaning beyond the schema — the default range and the multi-day overlap rule — but it does not clarify ordering or whether the range is inclusive.

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?

The description gives a specific verb (List) and resource (calendar events) and defines the visibility scope precisely: own, invited, and every event of shared calendars. This is enough to separate it from list_calendars (calendars rather than events) and from the create_/update_/delete_event siblings without opening any 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?

It clearly establishes the calling context: a day range for event retrieval, with an explicit default of today−365 to today+730 and an optional narrowing to a single shared calendar. It does not state exclusions or point at a sibling for discovering shared calendar names/ids, so the agent must infer how to obtain a valid `calendar` value.

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