Skip to main content
Glama
Sign In
teamwork

teamwork

by sondv5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Teamwork: update task

update_task

Update task details, assignees, tags, or completion status to reflect current project needs.

Instructions

Update fields of an existing task, or mark it complete with complete=true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "taskId": "<taskId>"
    },
    "name": "update_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
dueAtNoDue date, YYYY-MM-DD
tagIdsNoReplace the task's tags with these tag ids
taskIdYesTask to update
startAtNoStart date, YYYY-MM-DD
completeNoMark the task complete/incomplete
descriptionNo
assigneeUserIdsNoReplace the task's assignees with these user ids

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility. It states the operation is an update but does not disclose side effects such as whether unspecified fields are preserved, that tagIds and assigneeUserIds replace existing ones, or what the response contains. This is insufficient for a mutation tool.

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?

A single, well-structured sentence that front-loads the primary purpose and mentions a key option. No wasted words.

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 simple update tool with 8 parameters, the description is adequate but omits important behavioral context like replacement semantics and return values. It does not fully compensate for the absence of annotations.

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 75%, so most parameters already have clear meanings. The description adds no extra parameter details beyond what the schema provides, e.g., it does not emphasize replacement semantics for arrays.

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 clearly states the action ('Update fields of an existing task') and the resource (task), plus a specific use case (mark complete with complete=true). It naturally distinguishes from siblings like create_task or get_task.

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

Usage Guidelines4/5

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

It implies usage for existing tasks and highlights a special case (completion), but does not explicitly mention when not to use it or name alternatives. Given the context, the intended use is obvious.

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

Deploy Server

Other Tools