Acquire an advisory lock on a path for 5 minutes to signal other agents you're editing it. Calling again renews it; locks never block reads.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path to lock, relative to the workspace root. The file need not exist yet. | |
| workspace | No | Workspace slug. Optional, defaults to "temp". |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds valuable behavioral details: 5-minute expiry, renewal on repeated calls, and that locks never block reads. These go beyond the annotations without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences convey the core behavior, duration, renewal, and non-blocking nature. It is front-loaded with the verb 'Acquire' and contains no fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple and the description covers all essential aspects: purpose, duration, renewal, and non-blocking behavior. No output schema is needed for a lock operation, and the description is self-sufficient alongside the annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 does not add additional parameter semantics beyond the schema; it merely references 'a path' which is already described in the schema. No extra value is provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action: 'Acquire an advisory lock on a path for 5 minutes to signal other agents you're editing it.' It specifies the verb, resource, and purpose, and distinguishes itself from sibling 'unlock'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives clear context on when to use: 'to signal other agents you're editing it.' It also mentions renewal and non-blocking behavior. However, it doesn't explicitly state when not to use it or mention alternatives beyond implicit contrast with 'unlock'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct operation: file CRUD (write, read, edit, delete), versioning (history, restore), search (grep, list with q), locking (lock, unlock), uploads (request_upload, finalize_upload), and activity tracking. Even similar tools like request_upload and finalize_upload are complementary rather than overlapping.
Tool names are lowercase and action-oriented, with single-word verbs (read, write, delete) and two compound verbs (request_upload, finalize_upload) following a verb_noun pattern. This is consistent enough to be predictable, though the mix of single words and compound words is a minor deviation.
14 tools is well-scoped for a versioned file management server. Each tool covers a necessary aspect of the domain—file operations, version control, search, locking, uploads, and activity—without unnecessary bloat or missing critical functionality.
The tool set covers the full lifecycle of file management: create/write, read, edit, delete, restore, list, search, lock, unlock, upload/download (via request_upload/finalize_upload and read's download URL). The only potential gap is a copy operation, but that can be achieved with read+write. All workflows have no dead ends.
