Skip to main content
Glama
Sign In
Penpot MCP Server

Penpot MCP Server

by zcube
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

unlock_file_snapshot

Unlock a snapshot to enable its deletion. Pass the snapshot ID to remove the lock and allow the file to be removed.

Instructions

Unlock a snapshot to allow deletion

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": {
      "snapshotId": "<snapshotId>"
    },
    "name": "unlock_file_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
snapshotIdYesSnapshot ID to unlock

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of disclosure. It mentions the purpose (unlocking to allow deletion) but does not disclose potential side effects, idempotency, permission requirements, or behavior when the snapshot is already unlocked. The basic action is clear, but behavioral details are sparse.

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?

The description is a single, focused sentence with no filler words. Every word contributes to the meaning, making it highly concise and well-structured.

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 tool with one parameter and no output schema, the description is mostly adequate. It explains the tool's purpose and a key usage context (allowing deletion), but lacks any mention of prerequisites or edge cases. Given the simplicity, however, it is reasonably complete.

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 100%, so the parameter is fully documented in the schema ('Snapshot ID to unlock'). The description adds no additional meaning beyond the schema, matching the baseline for high schema 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?

The description clearly states the action ('Unlock') and the resource ('a snapshot'), and adds the purpose ('to allow deletion'), which distinguishes it from sibling tools like lock_file_snapshot, restore_file_snapshot, or delete_file_snapshot. It is specific and not a tautology.

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 'to allow deletion' implies the tool is used before deleting a locked snapshot, but it gives no explicit when-to-use or alternatives. There is no guidance on when not to use it or mention of lock_file_snapshot as the inverse operation, leaving the usage context only implied.

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

Deploy Server

Other Tools