Skip to main content
Glama

TaScan

by io.github.snowbikemike
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
tasksYesArray of tasks to create
list_idYesTask list (event) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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"
+]
  2. Changed1 schema field changed
    • 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"
+}
  3. Changed4 schema fields changed
    • 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"
+}
  4. Changed1 schema field changed
    • 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\"."
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only mark the operation as non-read-only and non-idempotent; the description adds crucial runtime behavior: permission requirements (agent:dispatch, with agent:dispatch:code variant), refusal without permission, and bulk-creation capability. There is no contradiction with the readOnlyHint=false/destructiveHint=false annotations.

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

Conciseness5/5

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

The description is compact and front-loaded: purpose first, then bulk capability, then the highest-risk parameter guidance, then sibling routing and permission warning. Each sentence earns its place and the IMPORTANT/NOTE formatting highlights the critical parts.

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?

The tool has a rich schema and no output schema; the description covers the main decision points (response_type, dispatch alternative, permissions) but does not describe the return value or failure modes beyond refusal. For a bulk creation tool this is a minor gap, so it is near-complete rather than fully complete.

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% and already contains detailed response_type guidance nearly verbatim (text for info collection, photo for proof, checkbox for confirmations). The tool description restates and emphasizes that guidance but does not add new meaning beyond the schema, so it stays at the high-coverage baseline of 3. The permission note is about authorization, not parameter semantics.

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?

The description opens with a specific action and target ('Add one or more tasks to an event (task list)') and notes bulk creation, so the agent knows exactly what the tool does. The note routing AI-agent dispatch to tascan_dispatch_to_agent also distinguishes this tool from a closely related sibling.

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?

It gives an explicit when-not instruction: 'To dispatch tasks to an AI agent use tascan_dispatch_to_agent instead.' It also warns that writing into an agent inbox list requires agent:dispatch permission and that the call is refused without it, giving clear conditions for use. This is strong routing guidance beyond the schema.

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

All TaScan toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources