tascan_add_tasks
ActiveTool of TaScan
declared in 1.3.0
Add one or more tasks to an event (task list). Supports bulk creation. IMPORTANT: Set response_type correctly — use "text" for info collection (names, phones, emails, notes), "photo" for visual verification (inspections, serial numbers, damage checks), "checkbox" only for simple confirmations. NOTE: To dispatch tasks to the Claude Code agent running on Mike's PC, use tascan_dispatch_to_agent instead — it routes directly to the agent's inbox with zero configuration needed.
Parameters schema
{
"type": "object",
"required": [
"list_id",
"tasks"
],
"properties": {
"tasks": {
"type": "array",
"items": {
"type": "object",
"required": [
"title"
],
"properties": {
"title": {
"type": "string",
"description": "Task title"
},
"description": {
"type": "string",
"description": "Task description"
},
"response_type": {
"enum": [
"checkbox",
"photo",
"text",
"number",
"date",
"choice"
],
"type": "string",
"description": "CRITICAL: \"text\" for names, phones, emails, notes, addresses, any free-form input. \"photo\" for tasks needing photographic proof (inspections, serial numbers, packed cases). \"checkbox\" ONLY for simple yes/no confirmations. \"number\" for numeric values. \"date\" for dates. \"choice\" for multiple-choice (needs response_config.options). Most info-collection tasks should be \"text\", most verification tasks should be \"photo\"."
},
"requires_photo": {
"type": "boolean",
"description": "Require photo on completion"
},
"is_safety_checkpoint": {
"type": "boolean",
"description": "Safety-critical task flag"
}
}
},
"description": "Array of tasks to create"
},
"list_id": {
"type": "string",
"description": "Task list (event) ID"
}
}
}No endpoints wrapped at confidence ≥ 0.70.
Parent server
TaScan
https://github.com/snowbikemike/tascan-mcp
1/7 registries