Quarterback
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QUARTERBACK_HOME | No | Directory for Quarterback data and config | |
| QUARTERBACK_API_URL | No | Optional Quarterback Pro API URL |
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
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_prioritiesC | Get prioritized list of tasks based on organizational context. |
| add_taskC | Add a new task with full metadata. |
| update_taskD | Update an existing task. |
| get_quick_winsC | Identify quick win tasks (high impact, low effort). |
| detect_conflictsC | Detect conflicting priorities and resource constraints. |
| assess_task_valueC | Assess whether a proposed task aligns with organizational goals. |
| get_blocking_tasksC | Get tasks that are blocking other work. |
| add_projectD | Add a new project. |
| list_projectsD | List all projects. |
| update_projectD | Update a project's properties. |
| get_organizational_summaryC | Get comprehensive organizational state summary. |
| add_advisory_documentC | Add a new advisory document for review and analysis. |
| list_advisory_documentsC | List advisory documents with filtering. |
| get_advisory_documentC | Get full details of a specific advisory document. |
| analyze_advisory_documentC | Analyze an advisory document against organizational context. |
| discuss_advisory_recommendationsD | Facilitate discussion about advisory recommendations. |
| adopt_advisory_recommendationsC | Approve or reject recommendations, optionally creating tasks. |
| register_webhookC | Register a webhook endpoint to receive task events. |
| list_webhooksB | List all registered webhooks. |
| update_webhookD | Update a webhook configuration. |
| delete_webhookC | Delete a registered webhook. |
| mark_task_agent_readyC | Mark a task for autonomous agent execution. |
| get_agent_ready_tasksC | Get tasks queued for agent execution. |
| update_agent_statusC | Update agent execution status of a task. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Organizational Goals | Current organizational goals and strategic priorities |
| Active Workflows | Workflow definitions and project groupings |
| Constraints | Resource constraints and strategic boundaries |
TDQS
Scored across 24 tools
Tools are well-differentiated across distinct domains: advisory document workflows (analyze/discuss/adopt), task intelligence (assess/value vs. priorities vs. quick wins), and agent orchestration (mark ready vs. update status). While several tools operate on tasks, their purposes—assessment, prioritization, blocking detection, and agent handoff—are clearly distinct.
Follows verb_noun convention consistently (add_task, analyze_advisory_document, detect_conflicts). Minor deviations exist: register_webhook breaks the add_* pattern used for other resources, and mark_task_agent_ready uses 'mark' instead of 'update' compared to update_agent_status, but these are readable exceptions rather than chaos.
With 24 tools, this pushes into the 'heavy' category (16-25 range) for a single server. While the domain (project orchestration + advisory workflows + agent execution + webhooks) justifies complexity, the surface area is large enough that agents may struggle to navigate the full set without careful prompting.
Strong coverage of advisory document lifecycles and agent orchestration, but notable gaps in basic CRUD: missing get_project and get_task (forcing reliance on list operations with filtering), and no delete operations for projects, tasks, or advisory documents. Webhooks also lack individual retrieval.