Skip to main content
Glama

task_update

Update task status, dependencies, owner, description, tags, and metadata within a project-based system for AI agents.

Instructions

Update an existing task's status, dependencies, or details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTask tags
ownerNoWho owns this task
statusNoNew status (deleted removes the task)
taskIdYesThe task ID to update
sourcesNoURLs, references, documentation used for this task (e.g. ['https://docs.example.com', 'Claude Code Plan Mode analysis'])
subjectNoBrief imperative title (e.g. 'Fix auth bug')
metadataNoMerge metadata keys into the task. Set a key to null to delete it.
addBlocksNoTask IDs that this task blocks
parent_idNoParent ID, task parent ID whom task is related to
project_idNoProject key this task belongs to
descriptionNoDetailed markdown description. When planning, document yourself regarding the task (e.g. search information online (use web_search tool if allowed), consult the codebase or ask further questions before delivering a plan). Preparing a plan can take several task update cycles until all the information is gathered. Structured description, details points when applicable: - Context: explain the why, and overall view how to solve the problem - Task details - Task location: where the task takes place (filepath or physical location, etc.) - Architecture: final structure of the expected output - Dependencies: explain what are required for delivery - Examples of the deliverable and expectations - Reasoning for the offered solution - Foreseen barriers and solution (from task context) - Implementation steps: real, commitable implementation steps, questions to ask the user for clarification and decision - Testing plan - Deployment plan - Sources and reference: explicitely list the sources used to design the plan, or say no sources have been used.
addBlockedByNoTask IDs to add as blockers
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It only mentions the update capability without noting any side effects, permissions, or rate limits. The schema's note about 'deleted' status is not repeated in the description.

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 sentence that is concise and free of unnecessary words. It efficiently communicates the core purpose.

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

Completeness2/5

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

Given the complexity (12 parameters, one required, no output schema), the description is too brief. It does not explain what the tool returns or how it behaves under various conditions, leaving significant gaps.

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%, so the baseline is 3. The description does not add significant meaning beyond the schema; it merely lists 'status, dependencies, or details' which is already evident from the parameter names and descriptions.

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 uses the specific verb 'Update' and clearly states the resource 'existing task' along with the aspects that can be updated ('status, dependencies, or details'), making it distinct from sibling tools like task_create or task_delete.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, when not to use it, or any prerequisites. The description only states what it does, not when to apply it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Skye-flyhigh/telos-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server