get_dev_task
Fetch a single dev-task by its ObjectID to view acceptance criteria, constraints, context pointers, and dependency information before starting work.
Instructions
Fetch a single dev-task by its ObjectID.
The response includes spec fields (acceptance_criteria, constraints, context_pointers), dependency info (for_agent, blocked_by), and slug. Read them before starting work. context_pointers short-circuits file discovery by telling you exactly which paths are relevant. Use the slug for all human-facing references (e.g. "work on task-42").
Args: task_id: The task's ObjectId hex string (24 hex chars). Use get_dev_task_by_slug if you have a slug like "task-42".
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"task_id": "<task_id>"
},
"name": "get_dev_task"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |