# Human Queue

Built-in escalation and human queue management. Exposes the escalation API as MCP tools for AI agents and remediation workflows.

| Property | Value |
|----------|-------|
| Server ID | `long-tail-human-queue` |
| Category | Automation |
| AI required | No |
| Credential providers | — |

## Compile Hints

escalate_and_wait creates a durable pause point. The step AFTER escalate_and_wait is always a signal step (kind: "signal") that receives the human response. Fields from the signal step output (e.g., password) must be wired via data_flow edges to ALL downstream steps that need them.

## Tools

### escalate_to_human

Create a new escalation for human review. Returns the escalation ID.

| | |
|---|---|
| Read-safe | No |

**Parameters:**

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| role | string | Yes | Target role for the escalation (e.g., "reviewer") |
| message | string | Yes | Description of what needs human review |
| data | object | No | Contextual data for the reviewer |
| type | string | No | Escalation type classification (default: "mcp") |
| subtype | string | No | Escalation subtype (default: "tool_call") |
| priority | number | No | Priority: 1 (highest) to 4 (lowest) (default: 2) |

### check_resolution

Check the status of an escalation. Returns status and resolver payload if resolved.

| | |
|---|---|
| Read-safe | Yes |

**Parameters:**

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| escalation_id | string | Yes | The escalation ID to check |

### get_available_work

List available escalations for a role. Returns pending, unassigned escalations.

| | |
|---|---|
| Read-safe | Yes |

**Parameters:**

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| role | string | Yes | Role to filter by |
| limit | number | No | Max results to return (default: 10) |

### claim_and_resolve

Claim an escalation and immediately resolve it with a payload. Atomic operation.

| | |
|---|---|
| Read-safe | No |

**Parameters:**

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| escalation_id | string | Yes | The escalation ID to claim and resolve |
| resolver_id | string | Yes | Identifier for who/what is resolving |
| payload | object | Yes | Resolution payload data |

### escalate_and_wait

Create an escalation and pause the workflow until a human responds. Returns a signal ID that the workflow uses to wait durably. Preferred over escalate_to_human + check_resolution polling.

| | |
|---|---|
| Read-safe | No |

**Parameters:**

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| role | string | Yes | Target role for the escalation (e.g., "reviewer") |
| message | string | Yes | Description of what input is needed from the human |
| form_schema | object | No | JSON Schema for the resolver form. Use format:"password" for sensitive fields. |
| data | object | No | Contextual data for the reviewer |
| assigned_to | string | No | Auto-assign to a specific user |
| type | string | No | Escalation type classification (default: "mcp") |
| subtype | string | No | Escalation subtype (default: "wait_for_human") |
| priority | number | No | Priority: 1 (highest) to 4 (lowest) (default: 1) |
