MemKernel

Overview Schema Source Related Servers Discussions Admin

memkernel_release_lease

Release a lease you hold on a file, using its fencing token, to make it available to other agents. Returns false if the token is stale or not yours.

Instructions

Release a lease you hold. Returns false if the token is stale (the lease expired and was granted to someone else) or not yours.

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": {
      "file_path": "<file_path>",
      "fencing_token": "<fencing_token>"
    },
    "name": "memkernel_release_lease"
  }
}

Input Schema

Name	Required	Description	Default
`file_path`	Yes
`fencing_token`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 16, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does usefully disclose that the call can fail with 'false' when the token is stale or belongs to another holder, which is real behavioral detail, but it says nothing about permissions, whether a repeat call is harmless, or how non-stale errors surface.

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?

Two short sentences, no filler, and the core action is front-loaded ahead of the failure caveat. Every clause carries information.

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

Completeness4/5

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

For a simple two-parameter lease operation with an output schema to cover the return shape, the description covers purpose and the main failure mode adequately. It is thin only on permissions and idempotency, which are not strictly needed to invoke it 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 0%, so the description must compensate. It partially does by explaining that the fencing_token can go stale when the lease is re-granted, which gives real meaning to that parameter, but file_path is never described and no format or expected-value guidance is offered.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Release a lease you hold') that is unambiguous and naturally separates it from the acquire_lease and heartbeat_lease siblings. It stops short of naming an alternative explicitly, so it is clear but not maximally differentiating.

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

Usage Guidelines3/5

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

The phrase 'you hold' implies the precondition (you must currently own the lease) and the second sentence sketches the failure context, but there is no explicit when-to-use / when-not guidance or named alternative for edge cases. Usage is left to inference.

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