Tirith

Official

Overview Schema Source Related Servers Discussions Admin

release

Idempotent

Give up held paths so other agents can claim them. Omit paths to release all; releases only exact matches, and does nothing if path not held.

Instructions

Give up leases so other agents can claim the paths; omit paths to release everything you hold. Use when you finish editing, not to extend time (renew) or to inspect (claims_list). Paths are matched exactly: releasing a file does not release a file#Symbol anchor inside it. not_found if you do not hold a named path, and then nothing is released.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`agent`	Yes	Your stable agent name.
`paths`	No	Paths to release. Omit to release everything you hold.

Output Schema

TableJSON Schema

Name	Required	Description
`agent`	No	The caller.
`status`	Yes	ok, or not_found when you do not hold a named path (nothing is released). invalid: bad input.
`message`	No	Human-readable detail, on most outcomes other than ok.
`released`	No	The paths released.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.1.2Sep 18, 2026

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

addedInput schema / properties / paths / description

Added value: +"Paths to release. Omit to release everything you hold."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Any result may also carry lost, inbox, inbox_more and persist_error; see guide.",
+  "properties": {
+    "agent": {
+      "description": "The caller.",
+      "type": "string"
+    },
+    "message": {
+      "description": "Human-readable detail, on most outcomes other than ok.",
+      "type": "string"
+    },
+    "released": {
+      "description": "The paths released.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "status": {
+      "description": "ok, or not_found when you do not hold a named path (nothing is released). invalid: bad input.",
+      "enum": [
+        "ok",
+        "conflict",
+        "not_found",
+        "none",
+        "invalid",
+        "cancelled"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedv1.1.1Sep 18, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description does not contradict them. It adds useful behavioral detail beyond annotations: exact path matching, the file#Symbol anchor nuance, and atomic not_found behavior where nothing is released. This is strong supplementary transparency.

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?

The description is compact at three sentences with no filler, and it front-loads the core purpose. The structure could be slightly smoother, but every sentence contributes necessary information about behavior, usage, or edge cases.

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?

Given only two parameters, a full-coverage schema, and a provided output schema, the description covers purpose, usage, alternatives, exact matching, error behavior, and release-all semantics. Nothing essential appears to be missing for an agent to invoke the tool correctly.

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. The description adds meaningful semantics beyond the schema: omitting paths releases everything held, path matching is exact, and releasing a file does not release embedded anchors. These details help the agent use the paths parameter 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: 'Give up leases so other agents can claim the paths', and clarifies the omit-paths release-all behavior. It also distinguishes this tool from siblings like renew and claims_list, so an agent can tell it apart without inspecting 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?

It explicitly states when to use the tool ('Use when you finish editing') and what not to use it for ('not to extend time (renew) or to inspect (claims_list)'). This gives clear, actionable routing guidance with named alternatives.

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