Skip to main content
Glama

ui_clear_active_edit

Clear a stale active-edit lock row so a file is no longer blocked by an outdated edit guard. Use it to resolve lock conflicts in work-plan project sessions.

Instructions

App-only: clear a stale active-edit lock row.

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": {
      "conv_id": "<conv_id>"
    },
    "name": "ui_clear_active_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
conv_idYes
repo_idNo
file_pathNo
project_idNo
workspace_dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses almost nothing. It never states that this is a destructive row deletion, whether it is reversible, what permissions or app context are required, or what happens when the lock is not actually stale and an edit is in flight.

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?

A single front-loaded clause with zero filler and the 'App-only' constraint stated first. It is efficient, though the brevity edges into under-specification rather than disciplined concision.

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

Completeness2/5

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

For a destructive lock-clearing tool with five undocumented parameters, no annotations, and no output schema, the definition leaves the agent without the safety and scoping information it needs. The 'App-only' and 'stale' qualifiers are the only things preventing a score of 1.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, and the description compensates for none of it. It does not explain what conv_id scopes, whether repo_id/file_path/project_id/workspace_dir narrow the lock lookup or are merely context, or what happens when they are omitted.

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

Purpose3/5

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

The verb+object pair 'clear ... active-edit lock row' names a concrete action and resource, and 'App-only' scopes it to the UI surface. However, the core concept 'active-edit lock row' is never unpacked, and nothing distinguishes this from other state-mutating siblings, so an agent must already know the lock model to be sure what is being cleared.

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

Usage Guidelines2/5

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

The word 'stale' implies the trigger condition (a lock left behind by an abandoned edit), which is a faint when-to-use hint. There is no guidance on how to detect staleness, no exclusion for locks held by a live edit, and no mention of any alternative or recovery path.

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