Tirith

Official

by eabz

Overview Schema Source Related Servers Discussions Admin

Rust

Local

task_list

Read-only

List board tasks by status or owner, newest first, to inspect progress without claiming work.

Instructions

List tasks on the board, filtered by status or owner, most recently updated first. Use to inspect the board without taking anything; to take work use task_pull. Rows are compact, 20 rows per page; pass next_before as before for older rows.

Input Schema

TableJSON Schema

Name	Required	Description
`agent`	Yes	Your stable agent name.
`limit`	No	Rows to return (default 20, max 200), most recently updated first.
`owner`	No	Only tasks owned by this agent.
`before`	No	Only tasks updated before this cursor: an RFC 3339 timestamp or a previous response's `next_before`.
`status`	No	Only tasks with this status.

Output Schema

TableJSON Schema

Name	Required	Description
`count`	No	Rows in this response.
`tasks`	No	Most recently updated first; null fields and empty arrays are omitted, ids shortened to 8 characters.
`total`	No	Rows that matched, across all pages.
`status`	Yes	ok. invalid: bad input.
`message`	No	Human-readable detail, on most outcomes other than ok.
`truncated`	No	True when older rows were left out.
`next_before`	No	Present when truncated: pass it back as before for the next older page.

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 / before / description

Added value: +"Only tasks updated before this cursor: an RFC 3339 timestamp or a\nprevious response's `next_before`."

addedInput schema / properties / limit / description

Added value: +"Rows to return (default 20, max 200), most recently updated first."

addedInput schema / properties / owner / description
```
Added value: +"Only tasks owned by this agent."
```
addedInput schema / properties / status / description
```
Added value: +"Only tasks with this status."
```

addedInput schema / properties / status / enum

Added value: +[
+  "todo",
+  "in_progress",
+  "blocked",
+  "done"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Any result may also carry lost, inbox, inbox_more and persist_error; see guide.",
+  "properties": {
+    "count": {
+      "description": "Rows in this response.",
+      "type": "integer"
+    },
+    "message": {
+      "description": "Human-readable detail, on most outcomes other than ok.",
+      "type": "string"
+    },
+    "next_before": {
+      "description": "Present when truncated: pass it back as before for the next older page.",
+      "type": "string"
+    },
+    "status": {
+      "description": "ok. invalid: bad input.",
+      "enum": [
+        "ok",
+        "conflict",
+        "not_found",
+        "none",
+        "invalid",
+        "cancelled"
+      ],
+      "type": "string"
+    },
+    "tasks": {
+      "description": "Most recently updated first; null fields and empty arrays are omitted, ids shortened to 8 characters.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Rows that matched, across all pages.",
+      "type": "integer"
+    },
+    "truncated": {
+      "description": "True when older rows were left out.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedv1.1.1Sep 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavioral context beyond that: it is non-destructive ('without taking anything'), it returns compact rows, it paginates at 20 rows per page, and it orders by most recently updated. It also explains the cursor semantics ('pass next_before as before'). This adds meaningful behavioral detail without contradicting the annotation.

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 sentences, no filler. The core purpose and ordering are front-loaded, the usage distinction comes second, and the pagination detail is last. Every sentence earns its place and the whole description is compact.

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?

For a read-only list tool with a 100%-covered schema and an output schema present, the description covers the essential behavioral aspects: what it lists, how it filters, how it orders, how pagination works, and when to use the sibling instead. Nothing an agent needs to call it correctly is missing.

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 all five parameters. The description adds a little extra meaning by explaining the pagination cursor relationship ('pass next_before as before') and the default/max row counts, but it doesn't need to compensate for any schema gaps. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description states a specific verb ('List'), a resource ('tasks on the board'), and two filtering dimensions (status or owner), plus an ordering rule (most recently updated first). It also distinguishes itself from the sibling task_pull by explicitly saying it is for inspection, not taking work. This is a clear, specific purpose that an agent can act on without opening the schema.

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?

The description explicitly says when to use this tool ('inspect the board without taking anything') and names the alternative for taking work ('to take work use task_pull'). It also gives pagination guidance ('pass next_before as before for older rows'). This is explicit when/when-not guidance with a named alternative, which is exactly what the dimension asks for.

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