MCP Node Tasks 05 - Sampling
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_taskA | Opretter en ny task i data/tasks.json |
| complete_taskB | Markerer en task som færdig ud fra id |
| sample_next_work_sessionA | Bruger MCP sampling til at få clientens LLM til at foreslå næste arbejdssession |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| all_tasks | Læs alle tasks fra data/tasks.json |
| open_tasks | Læs kun åbne tasks |
| project_guide | Læs projektets prioriteringsguide |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: creating a task, completing a task, and suggesting a next work session. No overlap or confusion possible.
All tools follow a consistent verb_noun pattern using snake_case: add_task, complete_task, sample_next_work_session. Predictable and clear.
With only 3 tools for a task management server, the count is slightly low but appropriate given the specialized focus on sampling-driven workflow. Not excessive or trivial.
Missing essential operations like listing tasks, deleting tasks, or updating task details. An agent cannot retrieve tasks to complete them, creating a significant gap in the workflow.