apex-memory

lease

Claim a document section and its subsections for a set time while drafting a long edit, blocking other agents’ conflicting writes until it expires or is released.

Instructions

Claim a section (and its subsections) while drafting a long edit, for minutes (1–60, default 15). Other agents' writes to it, its subsections or its ancestors are refused until it expires or is released; your own patch_section releases it. action: 'take' or 'release'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "lease"
  }
}

Input Schema

Name	Required	Description	Default
`path`	No
`action`	Yes
`heading`	No
`minutes`	No
`task_id`	No
`section_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Nov 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the exclusion set (the section, its subsections, and ancestors), that other agents' writes are refused, that the lease expires, and that patch_section releases it. It omits what happens when another agent already holds the lease — whether 'take' fails or queues — and whether leasing is identity-bound.

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 tight sentences, front-loaded with the core action and scope, followed by the consequence and the release mechanism. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter mutating coordination tool with no annotations and no output schema, the description should clarify how path/heading/section_id select the target and what a failed take looks like. The behavioral consequence and expiry semantics are covered well, but the addressing parameters and failure modes are not.

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 0%, so the description must compensate. It documents `minutes` thoroughly (range 1–60, default 15) and the two `action` values ('take'/'release'), but says nothing about `path`, `heading`, `task_id`, or `section_id`, or how those four identify the target section.

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 ('Claim') and resource ('a section (and its subsections)') plus the context ('while drafting a long edit'). It also distinguishes itself from the sibling patch_section by noting that patch_section releases the lease, so an agent can route between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for use ('while drafting a long edit') and names the implicit alternative path — your own patch_section releases the lease. It does not state when not to lease (e.g. for a quick single edit) or what to do if the take fails, but the when-to-use signal is unambiguous.

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

Deploy Server