alabasta
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALABASTA_RUN_ID | No | Correlates a resolution to an agent run (optional, used as externalRunId) | |
| ALABASTA_API_KEY | Yes | Workspace API key (alab_sk_...) generated in Alabasta settings | |
| ALABASTA_TASK_ID | No | Default task ID for this session (optional) | |
| ALABASTA_SITE_URL | Yes | The site URL of your Alabasta deployment (https://<deployment>.convex.site) |
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 |
|---|---|
| alabasta_get_taskA | Read an Alabasta task (title, description, status, priority) before editing. Pass taskId or identifier (e.g. TOM-24). |
| alabasta_list_my_tasksA | List tasks assigned to you, optionally filtered by status. |
| alabasta_start_task_workB | Mark a task in progress before you begin editing. |
| alabasta_collect_git_contextA | Gather real diff stat, commits, PR state, and CI checks from the local repo (git + gh). Call before submitting and merge the result into alabasta_submit_task_resolution. Best-effort — missing pieces are omitted. |
| alabasta_submit_task_resolutionA | Submit a STRUCTURED resolution after completing work. Moves the task to review for a human to accept — it never marks the task done and never edits the task description. Distinguish verified from unverified claims. Do not include conversational prompts. |
| alabasta_mark_ready_for_reviewA | Move a task into review without submitting a full resolution. |
| alabasta_report_blockerA | Record why the task could not be completed, for a human to triage. |
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 7 tools
Each tool targets a distinct action in the task workflow: reading, listing, starting work, gathering context, submitting a resolution, moving to review, and reporting blockers. No two tools overlap in purpose; even submit vs mark-ready are differentiated by whether a resolution is included.
All tools follow the consistent pattern alabasta_<verb>_<object> using snake_case. Verbs are specific and descriptive (get, list, start, collect, submit, mark, report), and objects clarify the target (task, git_context, resolution).
Seven tools is well within the ideal 3-15 range and each tool serves a necessary step in the workflow. The count is neither bloated nor sparse, and each tool has a clear role without redundancy.
The tool set covers the full lifecycle of task work: retrieve, list, begin, gather supporting context, submit outcome, escalate for review, or report a blocker. No critical workflow step is missing; the human-in-the-loop acceptance is intentionally outside the agent's scope but the agent has all needed actions to complete and hand off.