DontMynd

Move task

move_task

Move a task to this_week, next_week, or backlog. The task is placed at the end of the target list and its week is updated to match.

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": {
      "id": "<id>",
      "location": "<location>"
    },
    "name": "move_task"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Task id
`location`	Yes	Target location

Output Schema

Name	Required	Description	Default
`id`	Yes
`tag`	Yes
`title`	Yes
`week_id`	Yes
`location`	Yes
`position`	Yes
`created_at`	Yes
`updated_at`	Yes
`description`	Yes
`is_completed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "created_at": {
+      "type": "string"
+    },
+    "description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "type": "string"
+    },
+    "is_completed": {
+      "type": "boolean"
+    },
+    "location": {
+      "type": "string"
+    },
+    "position": {
+      "type": "number"
+    },
+    "tag": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "type": "string"
+    },
+    "updated_at": {
+      "type": "string"
+    },
+    "week_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "title",
+    "description",
+    "location",
+    "week_id",
+    "is_completed",
+    "position",
+    "tag",
+    "created_at",
+    "updated_at"
+  ],
+  "type": "object"
+}

First observedOct 28, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds real behavioral detail beyond that: the task is appended to the end of the target list and its week is synchronized, which explains the non-idempotent ordering side effect. It stops short of saying what happens if the task is already in the target location or what errors occur for an unknown id.

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 sentences, front-loaded with the action and destinations, followed by the side-effect sentence. Nothing is redundant or padded.

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?

An output schema exists and annotations cover the safety profile, so the description need not explain returns. It covers the core move semantics and ordering, but leaves edge cases (already-in-location behavior, invalid id handling) unaddressed for a mutation tool.

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 coverage is 100% with both parameters described and the location enum fully enumerated, so the schema carries the parameter semantics. The description only restates the enum values without adding format or validation detail, making the baseline 3 appropriate.

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?

States a specific verb (move) and resource (task) plus the three concrete destination values, so the operation is unmistakable. It does not explicitly differentiate itself from sibling update_task, which could plausibly also change a task's week, leaving a small ambiguity.

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 is implied by the enumerated destinations, so an agent can infer this is the tool for relocating a task between weeks. However, there is no explicit when-to-use/when-not guidance and no mention of update_task as the alternative for other field changes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DontMynd tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?