Skip to main content
Glama
putervision

state-memory-mcp

by putervision
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

manage_tasks

Prioritize runnable tasks, complete work, find blockers or stale tasks, and prune outdated items in branch-aware workflow state memory.

Instructions

Task prioritization, workflow execution, blockers, and stale task management (actions: next, complete, find_blocked, find_stale, find_blockers, find_similar_blockers, auto_prune). Use manage_tasks instead of query_graph when querying runnable tasks by priority order or resolving execution blockers.

Returns prioritized runnable tasks, blocker hierarchy, similar resolved blockers, or completion confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoNode type filter for find_stale.
limitNoMaximum tasks to return (1-1000).
queryNoQuery text for find_similar_blockers.
actionYesThe task management action to execute: next, complete, find_blocked, find_stale, find_blockers, find_similar_blockers, auto_prune.
statusNoStatus filter for find_stale.
node_idNoOptional node ID to check blockers for.
projectNoTarget project name or slug.
task_idNoTask node ID to complete.
thresholdNoSimilarity threshold for find_similar_blockers (0.0 - 1.0).
git_branchNoGit branch filter.
older_thanNoDuration threshold for staleness (e.g. 7d, 24h, 30m).
decision_idNoDecision node ID for find_blocked.
target_statusNoTarget status to assign when auto-pruning (e.g. cancelled).
artifact_titleNoOptional title of artifact produced on complete.
include_contextNoWhether to include parent plan/milestone and blocker context on next.
visual_state_idNoOptional visual state ID to link on complete.
artifact_metadataNoOptional metadata for produced artifact.
artifact_file_pathNoOptional file path for produced artifact.
include_transitiveNoWhether to include transitive blockers.
visual_relationshipNoVisual relationship for complete (default: renders_state).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.1
    • changedInput schema / properties / action / description
      Previous value: -"The task management action to execute."New value: +"The task management action to execute: next, complete, find_blocked, find_stale, find_blockers, find_similar_blockers, auto_prune."
    • addedInput schema / properties / action / enum
      Added value: +[
+  "next",
+  "complete",
+  "find_blocked",
+  "find_stale",
+  "find_blockers",
+  "find_similar_blockers",
+  "auto_prune"
+]
  2. Changed4 schema fields changedv1.2.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -true
    • removedInput schema / properties / artifact_metadata / additionalProperties
      Removed value: -{}
    • addedInput schema / required
      Added value: +[
+  "action"
+]
  3. Addedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false with destructiveHint=false, and the description is consistent with mutation-triggering actions (complete, auto_prune). It adds useful disclosure of what each action returns, which annotations do not cover. However, it says nothing about side effects of auto_prune, whether completion/pruning is reversible, or permission requirements for a tool whose default action set includes mutations.

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?

Three sentences, front-loaded with the action inventory then the routing rule then return values; no filler. It is dense but every sentence carries information, and the action list could arguably be deferred to the schema's enum.

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 a 20-parameter, multi-action tool with no output schema, the description supplies return-value orientation per action and a sibling-routing rule. The schema's per-parameter action scoping compensates for the missing action-to-parameter mapping. Remaining gap is the absence of any safety/reversibility note around the mutating actions.

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% and each param description already scopes itself to an action (e.g., 'for find_stale', 'for find_similar_blockers'), so the schema does the heavy lifting. The description adds no syntax, format, or default detail beyond the schema, so the baseline 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 enumerates the exact action set (next, complete, find_blocked, find_stale, find_blockers, find_similar_blockers, auto_prune) and names the resource domain, so an agent knows this is a task-lifecycle tool. It also differentiates itself from a sibling by name (query_graph). It stops short of a single crisp verb+resource statement, but coverage is strong.

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 gives an explicit routing rule: use manage_tasks instead of query_graph when querying runnable tasks by priority order or resolving execution blockers. That names an alternative and the selecting condition. It does not, however, explain when to prefer one action over another within the tool, nor any exclusions.

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