Tirith

Official

Overview Schema Source Related Servers Discussions Admin

contract_list

Read-only

List contracts filtered by consumer path or kind, newest first. Use this to find what a path depends on when you are not claiming it, with pagination via next_before.

Instructions

List contracts, filtered by a consumer path or by kind, most recently published first. Use to find what a path depends on when you are not claiming it, since a claim's brief already lists them; shapes come from contract_get. Rows are compact, 20 rows per page; pass next_before as before for older rows.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No	Only contracts of this kind.
`path`	No	Only contracts whose consumers overlap this path.
`agent`	Yes	Your stable agent name.
`limit`	No	Rows to return (default 20, max 200), most recently published first.
`before`	No	Only contracts published 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.
`contracts`	No	Most recently published first, compact: id, name, kind, consumers, current version. Shapes via contract_get.
`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 contracts published before this cursor: an RFC 3339 timestamp\nor a previous response's `next_before`."

addedInput schema / properties / kind / description
```
Added value: +"Only contracts of this kind."
```

addedInput schema / properties / kind / enum

Added value: +[
+  "http",
+  "function",
+  "type",
+  "event",
+  "cli",
+  "other"
+]

addedInput schema / properties / limit / description

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

addedInput schema / properties / path / description

Added value: +"Only contracts whose consumers overlap this path."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Any result may also carry lost, inbox, inbox_more and persist_error; see guide.",
+  "properties": {
+    "contracts": {
+      "description": "Most recently published first, compact: id, name, kind, consumers, current version. Shapes via contract_get.",
+      "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

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds useful behavioral details: pagination (20 rows per page, pass next_before as before for older rows) and ordering. No contradiction with the read-only hint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences front-load the core action and filters, then add usage context and pagination. 'Rows are compact' is slightly vague, but overall every sentence contributes and there is no fluff.

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?

The description covers filtering, ordering, pagination, and sibling alternatives. With an output schema present and read-only annotations, an agent has enough to select and call this tool correctly.

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 baseline is 3. The description reinforces path/kind filtering and cursor usage, but it does not add much semantic meaning beyond what the schema already documents for each parameter.

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 uses a specific verb and resource ('List contracts') and names the two filter dimensions ('consumer path or by kind') plus the sort order. It also distinguishes itself from contract_get by explicitly assigning shape retrieval to that sibling.

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 says when to use the tool ('when you are not claiming it') and gives the relevant alternative: a claim's brief already lists dependencies, and shapes come from contract_get. This is clear routing to alternatives without relying on inference.

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