Task Management MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tasksA | List all tasks |
| create_taskC | Create a new task |
| get_taskB | Get a specific task by ID |
| update_taskC | Update an existing task |
| delete_taskB | Delete a task |
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 5 tools
Each tool targets a distinct operation on tasks (create, delete, get, list, update) with no overlap, making them easy to differentiate.
All tools follow a consistent verb_noun pattern (e.g., create_task, delete_task), with only a minor pluralization in list_tasks, which still adheres to the pattern.
With 5 tools covering the core CRUD operations for task management, the count is well-scoped and appropriate for the domain.
The tool set provides full lifecycle coverage: create, read (single and list), update, and delete, with no obvious gaps for basic task management.