Skip to main content
Glama

dialogbrain

by com.dialogbrain
OverviewDiscussionsAdmin

tasks_update

Update a task. Set status='done' to complete it, 'cancelled' to cancel. Reassign with assignee. Status and assignee changes are recorded in the task's comment thread.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
due_atNoISO datetime
statusNo
summaryNoCompletion note (stored when marking done)
tag_idsNoTopics for the task: ids of workspace tags that apply to tasks (ai_tags.list with applies_to='task'). Replaces the current set; [] clears it.
task_idYesID of the task to update
agent_idNoAct as this agent instead of as yourself. Optional.
assigneeNoWho should do this: a workspace member (email, username, or user:<id> as workspace.members lists them), an AI agent (its name), or a contact (display name). Use 'me' for yourself. Call workspace.members to see who can be assigned. Where this listing offers assignee_user_id / assignee_agent_id / assigned_to_contact_id, they name an exact target instead.
priorityNo
descriptionNo
repeat_unitNoUnit for repeat_every.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
repeat_everyNoMake the task repeat: completing it creates the next occurrence, due this many repeat_unit after the previous deadline. E.g. repeat_every=3, repeat_unit='month' for quarterly. Pass repeat_every=0 to stop repeating.
clear_assigneeNoUnassign the task, returning it to the backlog
target_sessionNoWhich desktop Claude session should run this, by the name shown in workspace.desktops. Only needed when the assignee is an AI agent that runs on a machine and more than one session is connected — otherwise the task is not dispatched at all, rather than sent to a machine you did not mean.
assignee_user_idNo
assignee_agent_idNo
attachment_file_idsNoReplace the task's attachments with these file IDs
assigned_to_contact_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / assignee / description
      Previous value: -"Who should do this: a workspace member (email or username), an AI agent (its name), or a contact (display name). Use 'me' for yourself. Call workspace.members to see who can be assigned. For an exact target, pass assignee_user_id / assignee_agent_id / assigned_to_contact_id instead."New value: +"Who should do this: a workspace member (email, username, or user:<id> as workspace.members lists them), an AI agent (its name), or a contact (display name). Use 'me' for yourself. Call workspace.members to see who can be assigned. Where this listing offers assignee_user_id / assignee_agent_id / assigned_to_contact_id, they name an exact target instead."
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With annotations already declaring the mutation/isolation profile (readOnly=false, idempotent=false, destructive=false), the description adds a genuine behavioral trait not present in annotations: that status and assignee changes are recorded in the task's comment thread. This side-effect disclosure is exactly the kind of context annotations cannot carry, though it doesn't discuss rate limits or reversibility.

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?

Three short sentences with the core action front-loaded ("Update a task.") followed by the two most important semantic hints. Every sentence carries information; no filler or repetition of schema content.

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

Completeness3/5

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

For a 19-parameter mutation tool with no output schema, the description is thin: it ignores clear_assignee vs assignee, repeat_every/repeat_unit interplay, and the return behavior. The relatively rich schema descriptions partly fill the gap, and annotations cover the safety profile, so it is adequate but not 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 63%, and the schema already richly documents params like assignee, repeat_every, tag_ids, and target_session. The description only adds interpretation for the status enum values and confirms the assignee reassignment path, leaving the other ~17 params to the schema. It adds some meaning but does not compensate broadly.

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?

"Update a task" states a specific verb+resource, and the following sentences clarify the semantics of the status field (done=complete, cancelled=cancel) and reassignment. It is clearly distinguishable from tasks_create/tasks_get/tasks_list, but it never explicitly routes the agent away from a sibling or names alternatives.

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 implies usage via examples ("Set status='done' to complete it, 'cancelled' to cancel. Reassign with assignee.") — these are how-to instructions rather than when-to-use guidance. It offers no when-not-to-use, no prerequisites, and no comparison to sibling tools such as tasks_comment or agents_task_complete.

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

All dialogbrain 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