cuebit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_eventB | Create a new planning event (e.g. a meeting, milestone, deadline). |
| list_eventsA | List all events, optionally filtered by tag or date range. |
| get_eventA | Get full details of a single event by ID. |
| update_eventB | Update fields on an existing event. |
| delete_eventA | Delete an event and all its associated actions. |
| create_actionA | Create an action (task/to-do) that needs to be taken, optionally linked to an event. |
| list_actionsA | List actions, optionally filtered by status, assignee, priority, or linked event. |
| get_actionA | Get full details of a single action by ID. |
| update_actionC | Update an action — change its status, assignee, priority, due date, etc. |
| delete_actionC | Delete an action. |
| complete_actionC | Mark an action as done. |
| get_plan_summaryB | Get a high-level summary of all events and their associated actions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Tools are cleanly split between events and actions, with each resource having dedicated CRUD operations. The only mild overlap is between complete_action and update_action, since completion could be expressed as a status update, but the explicit purpose is clear enough.
All tool names follow a consistent verb_noun pattern: get/create/list/update/delete/complete plus event/action. The naming is predictable and makes the tool surface easy to navigate.
Twelve tools is well-scoped for a planning/event-and-action server. Each tool covers a distinct operation, and the count feels complete without being bloated.
The toolset provides full CRUD for both events and actions, plus a dedicated completion action and a summary endpoint. There are no obvious dead ends; the main workflows of creating, viewing, updating, and removing planning items are all covered.