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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
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 in functionality, making it easy for an agent to select the correct tool for any operation.
All tool names follow a consistent verb_noun pattern (add_task, complete_task, delete_task, list_tasks), using snake_case throughout. This predictability enhances usability and reduces confusion.
With 4 tools, this server is well-scoped for a task management domain, covering essential CRUD operations (create, read, update, delete) without unnecessary bloat. Each tool earns its place in the set.
The tool surface provides complete CRUD/lifecycle coverage for task management: add_task (create), list_tasks (read), complete_task (update), and delete_task (delete). There are no obvious gaps, allowing agents to handle all core workflows without dead ends.