task-mcp-node
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": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_taskC | Opretter en ny task i tasks.json. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_tasks | Hjælper med at prioritere tasks ud fra status og priority. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| all_tasks | Returnerer alle tasks fra den lokale tasks.json-fil. |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The single tool's purpose is clear.
The single tool uses a consistent verb_noun pattern (add_task), which is clear and predictable.
The server has only 1 tool, which is too few for the apparent scope of task management. Typically, such a server would need at least read, list, update, and delete operations.
The tool set is severely incomplete for task management, missing essential operations like reading, listing, updating, and deleting tasks. This will cause agent failures.