Skip to main content
Glama
adalekin

weeek-mcp

by adalekin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

weeek_set_task_parent

Nest a task under a new parent or detach it to top-level by setting parent_id to null. Position it among siblings using before or after task IDs.

Instructions

Nest a task under another one, or detach it with parent_id null. after/before place it among its new siblings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoSibling task id to sit after.
beforeNoSibling task id to sit before.
task_idYes
parent_idYesNew parent; null makes it top-level.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.2.2
    • addedInput schema / properties / after / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / after / type
      Removed value: -[
-  "integer",
-  "null"
-]
    • addedInput schema / properties / before / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / before / type
      Removed value: -[
-  "integer",
-  "null"
-]
    • addedInput schema / properties / parent_id / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / parent_id / type
      Removed value: -[
-  "integer",
-  "null"
-]
  2. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/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. It does disclose that parent_id null detaches the task and that after/before control sibling placement, which is useful mutation context. However, it omits permissions, reversibility, conflict handling when both after and before are supplied, and other side effects expected for a write operation.

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 two short sentences with no wasted words, and it front-loads the core operation before the ordering detail. Every phrase contributes to understanding the tool.

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 mutation tool with no annotations, no output schema, and one undocumented required parameter, the description is minimally adequate. It explains the core hierarchy and ordering behavior but provides no guidance on when to use it versus alternatives or how errors and edge cases are handled.

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 75%, with parent_id, after, and before already documented in the schema. The description adds only the combined behavior of nesting/detaching and sibling placement, and it does not document task_id, the one parameter lacking a schema description. It therefore adds marginal value beyond the structured fields.

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 states a specific verb and resource: 'Nest a task under another one, or detach it with parent_id null.' It also mentions ordering via after/before. However, it does not explicitly distinguish this tool from similar siblings like weeek_move_task, so it falls short of the top score for sibling differentiation.

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 description implies usage scenarios (nesting, detaching with null, ordering among siblings) but gives no explicit when-to-use guidance, no exclusions, and no alternatives. The agent can infer the basic case but gets no routing help against similar sibling tools.

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