Skip to main content
Glama
Sign In
Saga MCP

Saga MCP

by spranab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

subtask_reorder

Idempotent

Reorder subtasks for a task by submitting IDs in the desired sequence; unlisted subtasks are appended at the end preserving their relative order.

Instructions

Reorder a task subtask list. Pass IDs in the order you want; any omitted keep their relative order at the end.

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": {
      "task_id": "<task_id>",
      "ordered_ids": "<ordered_ids>"
    },
    "name": "subtask_reorder"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesParent task
ordered_idsYesSubtask IDs, in order

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark it idempotent and non-destructive; the description adds the useful behavior that omitted IDs keep their relative order at the end. No contradiction with 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?

Two short sentences that front-load the action, then clarify the only non-obvious detail. No filler.

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 simple two-parameter mutation, this covers invocation semantics well. It does not discuss edge cases like duplicate or foreign IDs, or return values, but these are not critical for selecting the tool correctly.

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?

Schema coverage is 100%, but the description adds the key array-order rule and explicitly instructs the caller to pass IDs in desired order, which is more than the schema's 'in order' note.

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?

Description uses a specific verb and resource: 'Reorder a task subtask list'. This clearly differentiates it from sibling subtask_create/update/delete tools.

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?

The use case is implied by 'reorder', and the partial-order semantics tell the agent how to supply IDs, but it never states when not to use it or points to an alternative for moving or updating subtasks.

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