Task 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_taskC | Add a new task to the task list |
| list_tasksA | List all tasks |
| complete_taskC | Mark a task as completed |
| delete_taskC | 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 4 tools
Each tool has a clearly distinct purpose: add_task creates new tasks, complete_task updates task status, delete_task removes tasks, and list_tasks retrieves tasks. There is no overlap or ambiguity between these four operations.
All tool names follow a consistent verb_noun pattern with snake_case (add_task, complete_task, delete_task, list_tasks). The naming is predictable and uniform throughout the set.
With 4 tools, this server is well-scoped for basic task management. Each tool earns its place by covering essential CRUD operations (create, read, update, delete) without unnecessary bloat.
The tool set provides complete CRUD/lifecycle coverage for task management: adding, listing, completing (updating status), and deleting tasks. There are no obvious gaps or dead ends for agents working with tasks.