dart-query
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DART_TOKEN | Yes | Your Dart AI token (starts with dsa_). Can be obtained from https://app.dartai.com/?settings=account |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| infoB | Progressive discovery of dart-query capabilities - start here |
| get_configA | Get workspace configuration: assignees, dartboards, statuses, tags, priorities, sizes |
| create_taskA | Create a new task with title, description, status, priority, size, dates, dartboard, assignees, tags, and task relationships (subtasks, blockers, related tasks) |
| list_tasksB | Query tasks with filters (assignee, status, dartboard, priority, tags, dates, has_parent), pagination, and detail levels. Parent filter uses client-side filtering. |
| get_taskA | Get a specific task by dart_id with optional comments and relationship details. Returns task relationships (subtasks, blockers, blocking, duplicates, related) with counts and optional expanded titles. |
| update_taskA | Update a task. Pass dart_id and any fields to change at the top level. Supports add_to/remove_from for incremental relationship changes and optional comment. Relationship arrays use full replacement unless using add_to/remove_from. |
| delete_taskA | Delete a task (moves to trash - recoverable via Dart web UI) |
| batch_update_tasksA | [Deprecated: use execute_dartql] Batch update multiple tasks matching a DartQL selector. Supports all task fields including relationships. CRITICAL: Always use dry_run=true first to preview changes! |
| batch_delete_tasksA | [Deprecated: use execute_dartql] Batch delete multiple tasks matching a DartQL selector. MOST DANGEROUS OPERATION! CRITICAL: dry_run defaults to true, confirm=true REQUIRED when dry_run=false. Tasks move to trash (recoverable). |
| execute_dartqlA | Execute DartQL UPDATE/DELETE statements. Supports template vars {field}, array literals, comments, and multi-statement (;). Dry-run by default. |
| get_batch_statusA | Retrieve status of a batch operation (update, delete, import, or dartql) by batch_operation_id. Operations are kept in memory for 1 hour. |
| import_tasks_csvA | Import tasks from CSV file with validation and parallel creation. CRITICAL: ALWAYS use validate_only=true first! Production safety: validate → fix errors → import. |
| list_docsA | List documents with optional filtering by folder, title_contains, text_contains. Supports pagination. |
| create_docB | Create a new document with title, text (markdown supported), and optional folder |
| get_docA | Get a specific document by doc_id with full text content |
| update_docA | Update an existing document (title, text, or folder). Validates references and only sends changed fields. |
| delete_docA | Delete a document (moves to trash - recoverable via Dart web UI) |
| search_tasksA | Full-text search across tasks with relevance ranking. Alternative to list_tasks for text-based discovery. Supports quoted phrases, exclusions (-term), and inline filters (dartboard:Name, status:Done, assignee:Name). |
| add_task_commentA | Add a comment to a task for status updates, AI rationale, or notes. Supports markdown formatting. |
| list_commentsA | List comments on a task with pagination. Token-efficient: returns minimal comment data. |
| move_taskA | Move/reposition a task within a dartboard or to a different dartboard. Supports ordering by index or relative to another task. |
| add_time_trackingB | Add a time tracking entry to a task. Supports started_at/finished_at or duration_minutes. |
| attach_urlA | Attach a file from URL to a task. URL must be publicly accessible. |
| get_dartboardB | Get details about a dartboard including task count. Token-efficient lookup. |
| get_folderA | Get details about a folder including doc count. Token-efficient lookup. |
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 25 tools
Most tools target distinct resources (tasks, docs, folders, config), but there is overlap between list_tasks and search_tasks (both find tasks, though one is filter-based and the other text-based). Also, batch_delete_tasks and batch_update_tasks are deprecated alternatives to execute_dartql, creating potential confusion about which to use. The descriptions do help clarify, but the presence of deprecated tools adds ambiguity.
Tool names follow a mostly consistent verb_noun pattern (get_task, update_task, create_task, delete_task, list_docs, etc.). Some deviations exist like 'execute_dartql' (non-noun object) and 'import_tasks_csv' (instead of import_tasks_csv_file or similar), but these are minor and the pattern is still readable.
With 25 tools, this is on the heavier side for a task management server. Many tools are focused on task lifecycle (create, get, update, delete, move, comment, time tracking), but some like batch operations and import seem redundant with execute_dartql. A few tools could be merged (e.g., batch_update and batch_delete into execute_dartql), but the count is not excessive given the domain complexity.
The server covers core CRUD for tasks (create, read, update, delete) and documents (create, read, update, delete), plus additional features like comments, time tracking, and URL attachments. However, there is no direct way to list or delete comments, and while tasks support relationships, there is no explicit tool to manage dartboard or folder creation/deletion (only get). The presence of deprecated tools suggests some operations are being consolidated, but the surface is fairly complete for task management with some gaps.