mcp-node-tasks-02-primitives
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_taskA | Opretter en ny task i den lokale JSON-fil |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_tasks | Giver en fast struktur til at analysere og prioritere tasks |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| all_tasks | Læs alle tasks fra den lokale JSON-fil |
TDQS
Scored across 1 tool
Only one tool exists, so there is no risk of ambiguity.
With a single tool, naming consistency is trivially perfect. The name 'add_task' follows a clear verb_noun pattern.
A single tool for task management is too few for reasonable functionality, making the server feel underdeveloped.
Only a create operation is provided, with no tools for listing, updating, deleting, or reading tasks, severely limiting usability.