Tirith

Official

by eabz

Overview Schema Source Related Servers Discussions Admin

Rust

Local

task_create

Add a todo task to a shared board for any agent to pull, with dependencies and priority to control when it runs.

Instructions

Add a todo task to the shared board for any agent to pull. depends_on holds it back until those tasks are done, higher priority is pulled first, and paths lets task_pull keep agents off each other's files. Use to queue work, not to start it: task_pull assigns work and task_update changes a task. Returns the task with its id.

Input Schema

TableJSON Schema

Name	Required	Description
`agent`	Yes	Your stable agent name.
`paths`	No	Paths the task will likely touch.
`title`	Yes	Short imperative title.
`priority`	No	Higher pulls first. Default 0.
`depends_on`	No	Task ids that must be done first.
`description`	No	What needs doing, for whoever pulls the task.

Output Schema

TableJSON Schema

Name	Required	Description
`task`	No	The new task: id, title, description, priority, depends_on, paths, created_by, created_at, updated_at, notes, and state: its status with owner (in_progress), owner and reason (blocked), or by (done).
`status`	Yes	ok. not_found: an unknown depends_on id. invalid: bad input or an ambiguous id prefix.
`message`	No	Human-readable detail, on most outcomes other than ok.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv1.1.2Sep 18, 2026

addedInput schema / properties / agent / description
```
Added value: +"Your stable agent name."
```
addedInput schema / properties / depends_on / description
```
Added value: +"Task ids that must be done first."
```

addedInput schema / properties / description / description

Added value: +"What needs doing, for whoever pulls the task."

addedInput schema / properties / paths / description

Added value: +"Paths the task will likely touch."

addedInput schema / properties / priority / description
```
Added value: +"Higher pulls first. Default 0."
```
addedInput schema / properties / title / description
```
Added value: +"Short imperative title."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Any result may also carry lost, inbox, inbox_more and persist_error; see guide.",
+  "properties": {
+    "message": {
+      "description": "Human-readable detail, on most outcomes other than ok.",
+      "type": "string"
+    },
+    "status": {
+      "description": "ok. not_found: an unknown depends_on id. invalid: bad input or an ambiguous id prefix.",
+      "enum": [
+        "ok",
+        "conflict",
+        "not_found",
+        "none",
+        "invalid",
+        "cancelled"
+      ],
+      "type": "string"
+    },
+    "task": {
+      "description": "The new task: id, title, description, priority, depends_on, paths, created_by, created_at, updated_at, notes, and state: its status with owner (in_progress), owner and reason (blocked), or by (done).",
+      "type": "object"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedv1.1.1Sep 18, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the sparse annotation (destructiveHint=false) by disclosing key behaviors: depends_on blocks until dependencies complete, higher priority is pulled first, paths help task_pull avoid file collisions, and the tool returns the created task with its id. It also clarifies the tool only queues work and does not start it.

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 tight sentences, front-loaded with purpose, then key behavior, then routing guidance. Every sentence earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and full parameter descriptions in the schema, the description is complete for an agent deciding whether and how to call it. It covers purpose, workflow semantics, alternative tools, and return value.

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 already 100%, so the baseline is 3. The description adds meaning on top by explaining the workflow effect of depends_on, priority, and paths in relation to task_pull, which the schema descriptions only partially convey.

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 opens with a specific verb and resource: 'Add a todo task to the shared board for any agent to pull.' It clearly differentiates from siblings by explicitly naming task_pull and task_update and stating what each sibling does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool vs alternatives: 'Use to queue work, not to start it: task_pull assigns work and task_update changes a task.' This gives an agent direct routing guidance between sibling tools.

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