Skip to main content
Glama
Local Development MCP Server

Local Development MCP Server

by lreb

update-task-status

Change an existing task's status to todo, in-progress, or done using its task ID to keep task tracking current.

Instructions

Update the status of an existing task

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>",
      "status": "<status>"
    },
    "name": "update-task-status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesNew status
taskIdYesTask ID (e.g. task-1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.9/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 the full behavioral burden, and all it adds is the word 'existing'. It does not say whether transitions are unrestricted (e.g. done back to todo), what happens for an unknown taskId or an invalid status value, what permissions are needed, or what the call returns. For a mutation tool with zero annotation coverage this is a significant gap.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, but its brevity is achieved by omission rather than by precision, so it falls short of a 5.

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 two-parameter mutation with full schema coverage and no output schema, the description is minimally sufficient: the agent knows what changes and which task. What is missing is failure behavior and any transition constraints, which matter for a write operation lacking 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 100%: both taskId and the enumerated status field are documented in the schema, including the example 'task-1'. The description adds no syntax or format meaning beyond that, so the baseline of 3 applies.

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?

The description gives a specific verb and resource ('Update the status of an existing task') plus the scope constraint that only an existing task qualifies. It therefore separates itself from create-task, delete-task, and list-tasks on behavior rather than relying on name alone, though it never names or contrasts an alternative explicitly.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The task is simple enough that an agent can usually infer the invocation from the verb, but the description itself supplies no routing logic at all.

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