DontMynd

Create task

create_task

Create a new task in this_week, next_week, or backlog. The task is added at the end of the list. Optionally assign an existing tag by name.

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": {
      "title": "<title>"
    },
    "name": "create_task"
  }
}

Input Schema

Name	Required	Description
`tag`	No	Existing tag name to assign
`title`	Yes	Task title
`location`	No	Where to create the task (default this_week)
`description`	No	Optional longer description

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 the create/non-idempotent/non-destructive profile, and the description usefully adds that new tasks are appended at the end of the list rather than positioned, which is real behavioral detail not in the schema. It doesn't say what happens on duplicate titles or whether the response returns the new task id, but with annotations covering safety this is above baseline.

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?

Three short sentences, front-loaded with the action and destination. Every sentence carries distinct information: creation targets, list placement, and optional tag assignment.

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 and full-coverage annotations mean the description needn't explain return values or safety. It covers placement, defaults, and tag preconditions; only duplicate-handling and tag-error behavior are unstated, which is a minor gap.

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 100%, so the schema already documents every parameter including the enum and the this_week default. The description restates the same facts (locations, optional tag) without adding syntax, format, or constraint detail beyond them, so baseline 3 applies.

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 ('Create a new task') plus the three valid destinations, so an agent knows exactly what the call produces. It does not explicitly distinguish itself from move_task or update_task, which share the same location vocabulary, leaving that routing to inference.

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 phrase 'assign an existing tag' implies a prerequisite (the tag must already exist, so create_tag may be needed first) but never states that condition or names the alternative. There is no explicit when-not guidance against update_task or move_task.

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?