sloppybee
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SLOPPYBEE_API_KEY | Yes | Your Sloppybee API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_listA | Create a new shareable task list. Can use AI to generate tasks or accept manual tasks. |
| get_listA | Retrieve an existing task list by its slug/URL identifier |
| generate_tasksA | Generate task suggestions using AI without creating a list. Useful for brainstorming. |
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 3 tools
Each tool serves a distinct purpose: create_list creates a new list, get_list retrieves an existing one, and generate_tasks provides standalone task brainstorming without list creation. While create_list can also generate tasks, the descriptions clearly separate the standalone generation use case.
All tool names follow a consistent verb_noun pattern: create_list, get_list, generate_tasks. The style is uniformly lowercase with underscores, making the set predictable and easy to navigate.
With only 3 tools, the set is minimal but appropriate for a focused task-list service focused on creation and retrieval. It slightly underutilizes the potential for a full CRUD surface, but the count is still within a reasonable range.
The domain implies task list management, yet the tools only support create and get operations. Missing update, delete, and list operations represent significant gaps that would prevent an agent from fully managing lists, leading to likely failures for common workflows.