Skip to main content
Glama
Sign In

TaScan

by io.github.snowbikemike
OverviewDiscussionsAdmin

tascan_update_task

Idempotent

Update a task (title, description, response_type, flags, sort_order). A task that sits in an AI agent inbox is agent input (the runner executes title + description), so ANY edit to it needs the agent:dispatch permission — agent:dispatch:code when the task is or becomes CODE:/SHELL:.

Input Schema

NameRequiredDescriptionDefault
titleNoNew title
task_idYesTask ID
sort_orderNoSort position
assigned_toNoWorker 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. Pass null to clear.
descriptionNoNew description
access_levelNoSR-S2: the task's own level (null = inherit the list); lowering needs an owner/admin-tier key
response_typeNoSee tascan_add_tasks for guidance. "text" for info collection, "photo" for visual proof, "checkbox" for yes/no only, "link" for the worker submitting a URL, "url" for the worker visiting a preset URL and confirming, "file" for the worker uploading a file.
requires_photoNoRequire photo
response_configNoResponse configuration. For "choice": {options: [...]}. See tascan_add_tasks.
required_equipmentNoEquipment this task depends on (free text)
is_safety_checkpointNoSafety-critical flag

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / access_level
      Added value: +{
+  "description": "SR-S2: the task's own level (null = inherit the list); lowering needs an owner/admin-tier key",
+  "enum": [
+    "open",
+    "assigned",
+    "secured",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Changed1 schema field changed
    • changedInput schema / 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"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / response_type / description
      Previous value: -"See tascan_add_tasks for guidance. \"text\" for info collection, \"photo\" for visual proof, \"checkbox\" for yes/no only."New value: +"See tascan_add_tasks for guidance. \"text\" for info collection, \"photo\" for visual proof, \"checkbox\" for yes/no only, \"link\" for the worker submitting a URL, \"url\" for the worker visiting a preset URL and confirming, \"file\" for the worker uploading a file."
    • changedInput schema / properties / response_type / enum
      Previous value: -[
-  "checkbox",
-  "photo",
-  "text",
-  "number",
-  "date",
-  "choice"
-]New value: +[
+  "checkbox",
+  "photo",
+  "text",
+  "number",
+  "date",
+  "choice",
+  "link",
+  "url",
+  "file"
+]
  4. Changed1 schema field changed
    • addedInput schema / 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. Pass null to clear.",
+  "type": "string"
+}
  5. Changed2 schema fields changed
    • addedInput schema / properties / required_equipment
      Added value: +{
+  "description": "Equipment this task depends on (free text)",
+  "type": "string"
+}
    • addedInput schema / properties / response_config
      Added value: +{
+  "description": "Response configuration. For \"choice\": {options: [...]}. See tascan_add_tasks.",
+  "type": "object"
+}
  6. Changed1 schema field changed
    • changedInput schema / properties / response_type / description
      Previous value: -"Task type"New value: +"See tascan_add_tasks for guidance. \"text\" for info collection, \"photo\" for visual proof, \"checkbox\" for yes/no only."
  7. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (idempotent, non-destructive), the description discloses a non-obvious behavioral fact: edits to an AI-inbox task are agent input and require agent:dispatch permission, escalating to agent:dispatch:code for CODE:/SHELL: tasks. This auth/safety context is exactly the kind of added value annotations cannot convey.

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?

Front-loaded with the operation and affected fields in one tight sentence. The second sentence is long but each clause (permission requirement plus the CODE:/SHELL: escalation) carries necessary information.

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 an 11-parameter mutation tool with a fully-described schema and no output schema, the description covers the what and the critical authorization behavior. Remaining nuances like access_level lowering and assigned_to semantics are fully handled in the schema, so nothing essential is missing.

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 coverage is 100% and the schema itself documents every parameter, including enums and nested response_config. The description only lists some field names, adding no meaning beyond the schema, so the baseline 3 is appropriate.

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

Purpose4/5

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

States a specific verb and resource ('Update a task') and enumerates the mutable fields, so the agent knows it is the task-editing operation. It does not explicitly contrast with tascan_update_subtask or tascan_complete_task, but the resource is unambiguous.

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

Usage Guidelines3/5

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

The description adds real context about prerequisites (agent:dispatch needed for any edit to an inbox task, agent:dispatch:code for CODE:/SHELL: tasks), which helps the agent know when the call will be authorized. However, it never names an alternative sibling or states when to prefer update_task over complete_task/update_subtask.

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
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.

Resources