TaScan

tascan_add_tasks

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 an AI agent use tascan_dispatch_to_agent instead. Writing into an agent inbox list requires the agent:dispatch permission (agent:dispatch:code for CODE:/SHELL: titles) — without it the call is refused.

Input Schema

TableJSON Schema

Name	Required	Description
`tasks`	Yes	Array of tasks to create
`list_id`	Yes	Task list (event) ID
`idempotency_key`	No	B1: optional replay key (up to 1024 chars, no braces) sent verbatim as the Idempotency-Key header instead of a fresh one per call — a retried call with the SAME key replays the original response instead of creating the tasks twice.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

changedInput schema / properties / tasks / items / properties / response_type / description

Previous value: -"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). \"link\" = the worker SUBMITS a URL (auto-verified by an http probe). \"url\" = the worker VISITS a preset URL and confirms. \"file\" = the worker uploads a file. \"signature\" = the worker reads a document and signs it with their passkey (attach the document with signature_doc_base64 and signature_doc_mime). Most info-collection tasks should be \"text\", most verification tasks should be \"photo\"."New value: +"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). \"link\" = the worker SUBMITS a URL (auto-verified by an http probe). \"url\" = the worker VISITS a preset URL and confirms. \"file\" = the worker uploads a file. \"signature\" = the worker reads a document, types their full name and signs with their passkey (Face ID / fingerprint); the name is signed with it (attach the document with signature_doc_base64 and signature_doc_mime). Most info-collection tasks should be \"text\", most verification tasks should be \"photo\"."

Changed4 schema fields changedOct 6, 2026

changedInput schema / properties / tasks / items / properties / response_type / description

Previous value: -"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). \"link\" = the worker SUBMITS a URL (auto-verified by an http probe). \"url\" = the worker VISITS a preset URL and confirms. \"file\" = the worker uploads a file. Most info-collection tasks should be \"text\", most verification tasks should be \"photo\"."New value: +"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). \"link\" = the worker SUBMITS a URL (auto-verified by an http probe). \"url\" = the worker VISITS a preset URL and confirms. \"file\" = the worker uploads a file. \"signature\" = the worker reads a document and signs it with their passkey (attach the document with signature_doc_base64 and signature_doc_mime). Most info-collection tasks should be \"text\", most verification tasks should be \"photo\"."

changedInput schema / properties / tasks / items / properties / response_type / enum

Previous value: -[
-  "checkbox",
-  "photo",
-  "text",
-  "number",
-  "date",
-  "choice",
-  "link",
-  "url",
-  "file"
-]New value: +[
+  "checkbox",
+  "photo",
+  "text",
+  "number",
+  "date",
+  "choice",
+  "link",
+  "url",
+  "file",
+  "signature"
+]

addedInput schema / properties / tasks / items / properties / signature_doc_base64

Added value: +{
+  "description": "Only with response_type signature: the document to be signed, base64 (PDF, PNG or JPEG, at most 10 MB). Uploaded after the task is created. Needs signature_doc_mime.",
+  "type": "string"
+}

addedInput schema / properties / tasks / items / properties / signature_doc_mime

Added value: +{
+  "description": "Media type of signature_doc_base64.",
+  "enum": [
+    "application/pdf",
+    "image/png",
+    "image/jpeg"
+  ],
+  "type": "string"
+}

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "B1: optional replay key (up to 1024 chars, no braces) sent verbatim as the Idempotency-Key header instead of a fresh one per call — a retried call with the SAME key replays the original response instead of creating the tasks twice.",
+  "type": "string"
+}

Changed4 schema fields changedSep 20, 2026

changedInput schema / properties / tasks / items / properties / response_type / description

Previous value: -"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\"."New value: +"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). \"link\" = the worker SUBMITS a URL (auto-verified by an http probe). \"url\" = the worker VISITS a preset URL and confirms. \"file\" = the worker uploads a file. Most info-collection tasks should be \"text\", most verification tasks should be \"photo\"."

changedInput schema / properties / tasks / items / properties / response_type / enum

Previous value: -[
-  "checkbox",
-  "photo",
-  "text",
-  "number",
-  "date",
-  "choice"
-]New value: +[
+  "checkbox",
+  "photo",
+  "text",
+  "number",
+  "date",
+  "choice",
+  "link",
+  "url",
+  "file"
+]

changedInput schema / properties / tasks / items / properties / subtasks / items / properties / response_type / description

Previous value: -"Typed subtask response. \"number\" for per-set values (reps/weight), \"text\" for notes, \"choice\" needs response_config.options. Default checkbox."New value: +"Typed subtask response. \"number\" for per-set values (reps/weight), \"text\" for notes, \"choice\" needs response_config.options. \"link\" = the worker submits a URL. \"url\" = the worker visits a preset URL and confirms. \"file\" = the worker uploads a file. Default checkbox."

changedInput schema / properties / tasks / items / properties / subtasks / items / properties / response_type / enum

Previous value: -[
-  "checkbox",
-  "number",
-  "text",
-  "choice"
-]New value: +[
+  "checkbox",
+  "number",
+  "text",
+  "choice",
+  "link",
+  "url",
+  "file"
+]

Changed1 schema field changedSep 2, 2026

addedInput schema / properties / tasks / items / properties / assigned_to

Added value: +{
+  "description": "Worker to assign this task to — pass the worker UUID (validated against your org and stored as the worker's name, which is how the worker portal matches \"my tasks\"). A plain name string is also accepted as-is.",
+  "type": "string"
+}

Changed4 schema fields changedAug 27, 2026

addedInput schema / properties / tasks / items / properties / required_equipment

Added value: +{
+  "description": "Equipment this task depends on (free text, e.g. \"88 lb kettlebells\")",
+  "type": "string"
+}

addedInput schema / properties / tasks / items / properties / response_config

Added value: +{
+  "description": "Response configuration. For \"choice\": {options: [\"A\",\"B\",\"C\"]}. For \"text\": {placeholder, multiline}. For \"number\": {placeholder}. For \"date\": {label, include_text}.",
+  "type": "object"
+}

addedInput schema / properties / tasks / items / properties / sort_order

Added value: +{
+  "description": "Explicit sort position (defaults to end of list, in array order)",
+  "type": "number"
+}

addedInput schema / properties / tasks / items / properties / subtasks

Added value: +{
+  "description": "Subtasks created with the task. Example set logging: [{title:\"Set 1\",response_type:\"number\"},{title:\"Set 2\",response_type:\"number\"},{title:\"Set 3\",response_type:\"number\"}]",
+  "items": {
+    "properties": {
+      "requires_photo": {
+        "type": "boolean"
+      },
+      "response_config": {
+        "description": "Same shape as task response_config",
+        "type": "object"
+      },
+      "response_type": {
+        "description": "Typed subtask response. \"number\" for per-set values (reps/weight), \"text\" for notes, \"choice\" needs response_config.options. Default checkbox.",
+        "enum": [
+          "checkbox",
+          "number",
+          "text",
+          "choice"
+        ],
+        "type": "string"
+      },
+      "title": {
+        "description": "Subtask title (e.g. \"Set 1\")",
+        "type": "string"
+      }
+    },
+    "required": [
+      "title"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedMar 5, 2026

changedInput schema / properties / tasks / items / properties / response_type / description

Previous value: -"Task type (default: checkbox)"New value: +"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\"."

First observedMar 4, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds real value beyond that: it discloses the required agent:dispatch permission (and agent:dispatch:code variant for CODE:/SHELL: titles) and states the call is refused without it. It does not describe return behavior, but no output schema exists and the auth disclosure is the important gap filled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, followed by clearly signposted IMPORTANT and NOTE blocks, so the key decision rules are easy to scan. It is slightly repetitive in echoing the schema's response_type guidance, which costs a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a bulk-create tool with no output schema, the definition covers purpose, the alternative tool, response_type selection, and the permission gate. The only omissions are return/error-shape details, which are minor given the annotation and schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description's response_type guidance largely restates what the schema already documents in detail, adding emphasis rather than new semantics; list_id and idempotency_key are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (add) plus resource (tasks) and scope (to an event/task list), and notes it supports bulk creation. It further distinguishes itself from the sibling tascan_dispatch_to_agent, so an agent can route correctly without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative (use tascan_dispatch_to_agent to dispatch to an AI agent) and the condition selecting it, plus concrete guidance on how to choose response_type. Both a when-not and a when-to-use rule are present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TaScan tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

tascan_add_tasks

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources