Skip to main content
Glama
spranab

Saga MCP

by spranab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subtask_update

Idempotent

Update a subtask's title, status, position, or dependency sets. Use force when a blocker no longer applies to start or finish despite unmet prerequisites.

Instructions

Update a subtask title, status or position. depends_on sets what it waits on, blocks the inverse; both replace the set, [] clears. Starting or finishing one with unmet prerequisites needs force.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
forceNoProceed despite unmet prerequisites. Only when a human says the blocker no longer applies, never on your own initiative. Logged.
titleNo
blocksNoSiblings that wait on this one — inverse of depends_on
statusNo
depends_onNoSiblings this one waits on (replaces the set)
sort_orderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.0
    • changedInput schema / properties / force / description
      Previous value: -"Proceed despite unmet prerequisites. Only when a human decided the blocker no longer applies — never on your own initiative. Logged."New value: +"Proceed despite unmet prerequisites. Only when a human says the blocker no longer applies, never on your own initiative. Logged."
  2. Changed4 schema fields changedv1.10.0
    • addedInput schema / properties / blocks
      Added value: +{
+  "description": "Siblings that wait on this one — inverse of depends_on",
+  "items": {
+    "type": "integer"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / depends_on
      Added value: +{
+  "description": "Siblings this one waits on (replaces the set)",
+  "items": {
+    "type": "integer"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / force
      Added value: +{
+  "default": false,
+  "description": "Proceed despite unmet prerequisites. Only when a human decided the blocker no longer applies — never on your own initiative. Logged.",
+  "type": "boolean"
+}
    • removedInput schema / properties / id / description
      Removed value: -"Subtask ID"
  3. First observedv1.5.3

TDQS

A3.9/5.0
Behavior4/5

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

The description adds valuable behavior beyond the annotations: depends_on and blocks are inverse relationship setters, both replace the existing set, [] clears, and force is required to bypass unmet prerequisites. It does not contradict the idempotentHint or destructiveHint annotations.

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?

The description is compact and information-dense. Three sentences cover the main purpose, relationship semantics, and the force requirement without wasted words, and the core update action is front-loaded.

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 7-parameter mutation tool with no output schema, the description covers the critical behavioral nuances: relationship replacement, clearing, and prerequisite enforcement. It does not describe return values or explicitly enumerate all status values, but the schema covers the enum and the essential calling context is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 43% schema description coverage, the description compensates meaningfully by explaining the semantics of depends_on, blocks, and force, including set replacement and clearing. It also maps 'position' to sort_order, but leaves id, title, and status mostly self-explanatory without deep detail.

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 clearly states a specific verb and resource: 'Update a subtask title, status or position.' It gives the core scope of the tool and distinguishes it from task-level siblings by focusing on subtasks, though it does not explicitly contrast it with subtask_reorder, which also deals with position.

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?

Usage context is implied rather than explicit: the description explains fields and force behavior, but does not state when to choose this tool over subtask_reorder or other subtask operations. The force caveat does give a concrete conditional for starting/finishing with unmet prerequisites.

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