Subconductor
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| init_checklistA | Initialize a new task checklist for the current subconductor run. This tool creates a task table with Status, ID, Name, and optional custom columns. It also natively sets up goal tracking to monitor completion progress. |
| activate_checklistA | Activate a previously initialized checklist by its goal name or a substring of it. The activated checklist will receive all subsequent task operations. |
| archive_checklistA | Archive a checklist by its goal name, a substring of it, or its numeric ID. The checklist will be moved to the archive directory and marked as Archived in the global index. |
| get_pending_taskA | Retrieve the next single pending task from the active checklist. Returns "DONE" if all tasks are finished. Tasks are returned with an ID (e.g., "(#1) Task Name") which can be used to reference them efficiently. |
| mark_task_doneA | Mark a specific task as completed in the active checklist. You can reference the task by its ID (e.g., "1" or "#1") for efficiency, or by its full name. You can optionally provide a note detailing the progress or result. |
| unmark_taskA | Revert a completed task back to pending status in the active checklist. You can reference the task by its ID (e.g., "1" or "#1") or by its full name. Any completion notes will be removed. |
| add_taskB | Add a new task to the active checklist. The task is appended to the end of the list and automatically assigned a new ID. |
| remove_taskA | Remove a task from the active checklist. Warning: Removing a task will automatically re-index the IDs of all subsequent tasks in the checklist. |
| get_pending_tasksA | Retrieve a batch of multiple pending tasks from the active checklist. Tasks are returned with an ID (e.g., "(#1) Task Name") which can be used to reference them efficiently. This is useful for getting an overview of upcoming work or for efficiently processing multiple simple tasks in a single turn. |
| mark_tasks_doneA | Mark multiple tasks as completed in a single batch operation. You can reference tasks by their ID (e.g., "1" or "#1") or by their full name. This is efficient when several tasks are finished simultaneously. Like mark_task_done, you can optionally provide a note for each task to document progress or results. |
| unmark_tasksA | Revert multiple completed tasks back to pending status in a single batch operation. You can reference tasks by their ID (e.g., "1" or "#1") or by their full name. |
| add_tasksA | Add multiple new tasks to the active checklist. Tasks are appended to the end of the list and automatically assigned new IDs. |
| remove_tasksA | Remove multiple tasks from the active checklist. Safe for batch deletion, as remaining tasks are dynamically re-indexed only after all specified removals are processed. |
| alertA | Trigger a desktop notification with a custom title, message, and severity level (info, warn, error). This is useful for providing immediate feedback on background task completion or issues. |
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 14 tools
Each tool has a clearly distinct purpose: operations on checklists (init, activate, archive) and tasks (add, get, mark, remove, unmark) are well-separated, including singular/plural variants for batch operations. The alert tool is unrelated but not overlapping.
Most tools follow a consistent verb_noun pattern (e.g., add_task, mark_task_done). The only deviation is 'alert', which lacks a noun, and 'init' instead of 'initialize', but these are minor and do not cause confusion.
With 14 tools, the server covers all essential operations for checklist management without unnecessary bloat. The count fits well within the typical 3-15 range for a focused domain.
The toolkit covers the full lifecycle of checklists and tasks (create, read, update, delete). Minor gaps exist, such as no tool to list all checklists or update task content, but core workflows are supported.