Skip to main content
Glama
Sign In
Saga MCP

Saga MCP

by spranab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

subtask_delete

DestructiveIdempotent

Delete one or more subtasks by ID. Pass an array of IDs to remove them from the project tracker.

Instructions

Delete one or more subtasks. Accepts a single ID or array of IDs.

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": {
      "ids": "<ids>"
    },
    "name": "subtask_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesSubtask IDs to delete — e.g. [4, 7]. Always an array, even for one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.10.0
    • addedInput schema / properties / ids / description
      Added value: +"Subtask IDs to delete — e.g. [4, 7]. Always an array, even for one."
    • addedInput schema / properties / ids / items
      Added value: +{
+  "type": "integer"
+}
    • removedInput schema / properties / ids / oneOf
      Removed value: -[
-  {
-    "description": "Single subtask ID",
-    "type": "integer"
-  },
-  {
-    "description": "Multiple subtask IDs",
-    "items": {
-      "type": "integer"
-    },
-    "type": "array"
-  }
-]
    • addedInput schema / properties / ids / type
      Added value: +"array"
  2. First observedv1.5.3

TDQS

C2.6/5.0
Behavior2/5

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

The annotations (destructiveHint=true, readOnlyHint=false, idempotentHint=true) already cover the core safety profile. The description adds no side-effect context such as permanence, cascade behavior, or error behavior, and its only extra behavioral claim—accepting a single ID—is false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is short and front-loaded, but the second sentence does not earn its place: it repeats schema information and introduces an inaccuracy. A clean one-sentence description that just said 'Delete one or more subtasks by ID' would be better.

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?

For a one-parameter delete with no output schema, the core requirements are mostly covered by the schema, but the description introduces a conflicting input format and omits any return or error semantics. An agent cannot reliably know what happens after deletion.

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

Parameters1/5

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

The schema fully documents ids at 100% coverage and explicitly says 'Always an array, even for one.' The description directly contradicts this by saying it accepts a single ID, which could cause an agent to send an integer instead of an array. This is actively harmful.

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 opens with a specific verb and target: 'Delete one or more subtasks.' This tells an agent exactly what the tool does and is enough to distinguish it from task_delete, note_delete, and comment_delete without inspecting the schema.

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 given about when to prefer this tool over alternatives such as task_delete, subtask_update, or subtask_reorder. There are no exclusions, prerequisites, or context cues beyond what the name implies.

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