Skip to main content
Glama
Sign In
killbottleneck-mcp

killbottleneck-mcp

Official
by tengolabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

list_calendars

Retrieves shared calendars for company events, bookable resources, and time off, including kind, color, write access, and approval needs. Read-only.

Instructions

List the shared calendars of the instance — company events (shared), rooms and other bookable things (resource), vacations and time off (absence) — with kind, color, who may add entries (write_access) and whether time off needs approval. 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_calendars"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are supplied, so the description carries the burden and does so for the most important trait by stating 'Read-only' explicitly. It also discloses the response contents (kind, color, write_access, approval requirement), compensating for the absent output schema; only pagination/auth details are missing, which is minor for a zero-parameter instance-level list.

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 sentence, front-loaded with the action and resource, with the kind enumeration and returned fields parenthesized compactly and the safety note last. No filler wording.

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?

With no output schema, the description must describe the return shape and it does by naming four returned attributes. Nothing about ordering, result size, or what to do with write_access is explained, but those are minor for this simple read tool.

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?

The tool takes no parameters, so there is no parameter meaning to add and the schema is trivially complete. Baseline 4 applies.

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?

States a specific verb and resource ('List the shared calendars of the instance') and enumerates the three calendar kinds it covers (shared, resource, absence), which an agent can map directly onto the sibling list_events/create_calendar pair.

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

Usage Guidelines3/5

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

Usage is only implied: the enumeration of calendar kinds suggests this is the discovery step before listing events or creating a calendar, but the description never says when to call it, when not to, or names any alternative tool.

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