TaskBullet
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASKBULLET_API_KEY | Yes | Your TaskBullet API key (starts with tb_live_). Required to authenticate with the TaskBullet Agent API. | |
| TASKBULLET_API_BASE | No | Override the TaskBullet API base URL for self-hosted or staging environments. | https://taskbullet.com/api/v1 |
| TASKBULLET_SOURCE_AGENT | No | Audit label for which agent originated the request. | mcp-client |
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 |
|---|---|
| get_balanceA | Return remaining VA hours on this account and whether delegate_task will be accepted. Call this before proposing spend. Does not create a task. |
| delegate_taskA | Call get_balance first, then confirm with the user before sending (real hours) unless they already said to send it. Delegate a task to a real human virtual assistant when the AI cannot complete it autonomously. Use this for phone calls, 2FA-gated logins, physical-world actions, subjective QA, manual data entry, or anything else outside the model's reach. Returns a taskId for tracking. |
| list_tasksB | List recently delegated tasks for this account, optionally filtered by status. Use to check progress on prior delegations. |
| get_taskA | Get the current status, completion timestamp, and result notes for a specific delegated task. |
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 4 tools
Each tool targets a distinct action: checking balance, creating a delegation, listing tasks, and retrieving one task. There is no meaningful overlap; list_tasks and get_task are clearly differentiated by collection vs. single item.
All tool names follow a consistent snake_case verb_noun pattern: get_balance, delegate_task, list_tasks, get_task. The pattern is predictable and easy to scan.
Four tools are well-scoped for a focused delegation service. Each tool serves a clear purpose in the workflow: precheck, create, list, and inspect.
The core lifecycle is covered: check balance, delegate a task, list tasks, and get task details. Minor gaps like canceling or updating a delegated task are absent, but agents can work around them for most workflows.