Skip to main content
Glama

Release draft edit lock

release_guide
Idempotent

Release this process's edit lock on a draft guide so you can switch drafts or hand authoring to another process; safe when no lock is held and blocks releasing another process's lock.

Instructions

Explicitly release this server process's edit lock on a draft, for example when switching to another draft or handing authoring to another teach-me process. Idempotent when no lock is held; refuses to release a lock owned by another process. Finished guides do not need a lock.

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": {
      "guide_id": "<guide_id>"
    },
    "name": "release_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
guide_idYesDraft guide id (g_...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/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, so the description earns credit for adding what the annotations do not: the lock is process-scoped, a no-op when no lock is held, and it refuses to release a lock owned by another process. It does not describe the failure surface (error vs silent no-op) or what is returned, leaving a small gap.

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 short sentences with the action and scope front-loaded, followed by the triggering example, then the safety/ownership constraint and the exemption. No sentence is filler.

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 single-parameter lock-release operation with annotations covering idempotency and non-destructiveness, the description covers scope, rationale, and the ownership refusal. Only the outcome of a refusal (error type or return signal) is unspecified, and with no output schema that is a minor omission.

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?

Only one parameter and schema coverage is 100%, so the schema already documents 'guide_id' with the g_... format. The description adds the notion of a 'draft' guide id only implicitly; otherwise it does not enrich parameter meaning beyond the schema, which is baseline for high coverage.

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 and resource ('release this server process's edit lock on a draft') and scopes ownership to this process, which an agent can immediately distinguish from siblings like finish_guide or select_guide that touch a guide's lifecycle rather than a lock.

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 concrete triggering situations ('switching to another draft or handing authoring to another teach-me process') and an implicit exclusion ('Finished guides do not need a lock'). It stops short of naming a specific sibling alternative to call instead, but the conditions are clear enough to select correctly.

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