Tirith

Official

Overview Schema Source Related Servers Discussions Admin

decision_list

Read-only

Search recorded decisions by affected path or text query to avoid duplicating prior choices before recording new ones. Results are paginated, newest first, and support filtering by path or case-insensitive terms.

Instructions

List recorded decisions, filtered by an affected path or a case-insensitive text query over title, decision and rationale, newest first. Use before decision_record so nothing is decided twice; a claim's brief already carries the decisions for the paths it claims. 20 rows per page; pass next_before as before for older rows.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	No	Only decisions affecting this path.
`agent`	Yes	Your stable agent name.
`limit`	No	Rows to return (default 20, max 200), newest first.
`query`	No	Case-insensitive text to search for.
`before`	No	Only decisions recorded before this cursor: an RFC 3339 timestamp or a previous response's `next_before`.

Output Schema

TableJSON Schema

Name	Required	Description
`count`	No	Rows in this response.
`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.
`decisions`	No	Newest first: id, title, decision, rationale, alternatives, affects_paths, recorded_by, recorded_at.
`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.

Changed6 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 decisions recorded before this cursor: an RFC 3339 timestamp\nor a previous response's `next_before`."

addedInput schema / properties / limit / description

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

addedInput schema / properties / path / description

Added value: +"Only decisions affecting this path."

addedInput schema / properties / query / description

Added value: +"Case-insensitive text to search for."

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"
+    },
+    "decisions": {
+      "description": "Newest first: id, title, decision, rationale, alternatives, affects_paths, recorded_by, recorded_at.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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"
+    },
+    "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.7/5.0

Behavior4/5

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

The readOnlyHint annotation already marks it as safe/read-only, and the description adds meaningful behavioral detail beyond that: case-insensitive search scope, newest-first ordering, 20-row default page size, and how to retrieve older rows using next_before. This gives the agent a solid model of the tool's runtime behavior 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 deliver the core capability, the primary use case and alternative, and pagination behavior with no filler. Key information is front-loaded, and every sentence earns its place.

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 filtered, read-only list tool, nothing essential is missing: it explains what is listed, how to filter, how results are ordered, how pagination works, and when to prefer it over decision_record. The output schema covers return values, and the annotations cover the read-only safety profile.

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 100%, so the baseline is 3, but the description adds value by clarifying that query searches title, decision, and rationale, and by explaining that next_before from a prior response should be passed as before for older pages. This goes beyond the schema's terse descriptions and helps the agent use the parameters correctly.

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 opens with a specific verb and resource: 'List recorded decisions', then states the filtering modes (affected path or case-insensitive query over title, decision, rationale) and ordering (newest first). It also distinguishes itself from the sibling decision_record, so an agent can tell them apart immediately.

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?

It gives explicit usage direction: 'Use before decision_record so nothing is decided twice', which names the alternative and the condition for using this tool. It also notes that a claim's brief already carries decisions for claimed paths, providing a clear when-not-to-use signal, while pagination instructions further clarify how to invoke it.

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