tasq
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASQ_DB | No | The path to the SQLite database file. Defaults to $XDG_DATA_HOME/tasq/tasks.db. | |
| TASQ_CONFIG | No | Path to the TOML configuration file. Defaults to $XDG_CONFIG_HOME/tasq/config.toml. | |
| TASQ_DAILY_HOURS | No | Override the daily focus hours for planning. Default from config. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_taskA | Create a task. |
| edit_taskA | Update a task. Omit a field to leave it unchanged; pass an empty string
to clear an optional field (description, project, size, dates). Set
|
| link_sessionA | Link the AI agent session you're working in to a task, so it can be
resumed later. |
| unlink_sessionA | Remove the AI session link from a task. |
| flag_attentionA | Flag a task as awaiting the user's attention — e.g. you need a decision
or input to proceed. |
| clear_attentionA | Clear a task's 'needs attention' flag once the user has responded. |
| ingestA | Sync external items into tasks, deduplicated by (source, external_id). |
| get_taskC | Full task detail including status history and extracted references. |
| list_tasksB | List tasks with structured filters. By default terminal tasks
(completed/cancelled) are hidden unless |
| search_tasksA | Fuzzy-search tasks over title and description; ranked, best first. |
| search_referencesB | Search URLs extracted from task descriptions (fuzzy on url + anchor). |
| transition_taskA | Change a task's status, recording the transition (comment optional). Statuses: waiting, in_progress, blocked, completed, cancelled. |
| agendaC | Overdue, today, upcoming (next N days), and in-progress/blocked tasks. |
| planA | Propose a non-persistent day-by-day schedule of open tasks, greedily
packed into a daily focus budget (default from config) and ordered by
started-then-priority-then-due. Counts working days — weekends are skipped
unless |
| add_projectC | Create a project. Project labels describe the project (e.g. the company). |
| list_projectsD | List projects. |
| archive_projectA | Archive a project (kept, not deleted). |
| list_labelsA | List labels WITH descriptions — read these to know what each label means and when to apply it before labelling or prioritising. |
| describe_labelA | Set or update a label's description (creates the label if new). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| labels_resource | The full label taxonomy with descriptions, as Markdown context. |
| agenda_today_resource | |
| agenda_upcoming_resource |
TDQS
Scored across 19 tools
Each tool targets a distinct resource and action: tasks, projects, labels, sessions, attention flags, and bulk ingestion. Overlap is minimal, and descriptions clearly distinguish search_tasks from search_references and agenda from plan.
Most tools follow a clear verb_noun pattern (add_task, list_tasks, edit_task, link_session). A few exceptions like 'ingest', 'agenda', and 'plan' deviate from this pattern but remain readable and predictable.
With 19 tools covering task CRUD, status transitions, projects, labels, sessions, and planning, the count is well-scoped for the server's purpose. It is neither overly sparse nor bloated.
The surface covers most lifecycle needs: create/read/update/transition tasks, manage projects and labels, link sessions, and flag attention. Minor gaps exist, such as no hard delete for tasks and no session listing, but these are workable.