Tirith

Official

Overview Schema Source Related Servers Discussions Admin

claims_list

Read-only

Check live leases before claiming a path: see who holds it and until when, or list all active claims. Use it to avoid conflicts and find expired-free paths.

Instructions

List live leases: by default yours plus any lease overlapping path, which is what a conflict check needs; all=true lists the whole board. Use before claim to see who holds a path and until when; for counts and daemon health use status. Expired leases are never listed. Newest first, 20 rows per page; pass next_before as before for older rows.

Input Schema

TableJSON Schema

Name	Required	Description
`all`	No	List every live claim, not just yours and those overlapping `path`.
`path`	No	Also include claims overlapping this path, whoever holds them.
`agent`	Yes	Your stable agent name.
`limit`	No	Rows to return (default 20, max 200), newest first.
`before`	No	Only claims older than 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.
`claims`	No	id, owner, paths, reason, claimed_at, expires_at, ttl_secs. Expired claims are never listed.
`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.

Changed6 schema fields changedv1.1.2Sep 18, 2026

addedInput schema / properties / agent / description
```
Added value: +"Your stable agent name."
```

addedInput schema / properties / all / description

Added value: +"List every live claim, not just yours and those overlapping `path`."

addedInput schema / properties / before / description

Added value: +"Only claims older than 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), newest first."

addedInput schema / properties / path / description

Added value: +"Also include claims overlapping this path, whoever holds them."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Any result may also carry lost, inbox, inbox_more and persist_error; see guide.",
+  "properties": {
+    "claims": {
+      "description": "id, owner, paths, reason, claimed_at, expires_at, ttl_secs. Expired claims are never listed.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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"
+    },
+    "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

A5/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses important behavior: expired leases are never listed, newer leases come first, pagination defaults to 20 rows, and next_before drives older-result pagination. This gives the agent a clear model of what the call returns and its limits.

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?

Four dense sentences carry purpose, scope, usage guidance, exclusions, ordering, and pagination with zero filler. The most important scoping information is front-loaded.

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 listing tool with full schema coverage and an output schema, this description covers selection criteria, sibling routing, exclusions, ordering, and pagination. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds real semantic value by explaining the default behavior of path and all, the meaning of all=true, and how before consumes next_before for pagination. It connects parameters to behavior rather than repeating schema names.

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?

States a specific verb and resource: 'List live leases' with precise default scope ('yours plus any lease overlapping path') and the conflict-check purpose. It distinguishes itself from siblings like claim and status, so an agent can tell it apart without opening schemas.

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 routes usage: 'Use before claim to see who holds a path and until when; for counts and daemon health use status.' This gives both when-to-use and an alternative, leaving nothing to inference.

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