Skip to main content
Glama
ostapondo

plonk-mcp

by ostapondo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

save_zone_set

Create or replace named zone sets for drag snapping. Define rectangle zones, optional names, gaps, and assign to a screen for immediate use.

Instructions

Create or replace a named zone set used for drag snapping. Zones are rectangles {x,y,w,h} as fractions 0..1 of a screen's visible area, origin TOP-LEFT; each zone must stay inside the screen, but zones may overlap each other (the smallest one under the cursor wins). A zone may also carry a 'name' ('chat', 'editor'): it is drawn under the zone's number, the user can say it out loud, and snap_window takes it instead of the number; names must be unique within the set, ignoring case, and cannot be a bare number. Pass 'screen' to also assign the set to that monitor so it becomes active immediately. Pass 'gap' to give this set its own spacing around windows in points, or null to make it follow the default gap again; omitting it keeps whatever the set had. Built-in sets already exist: Halves, Thirds, 60 / 40, Quarters, Priority.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gapNoThis set's own gap in points; null follows the default gap (get_state.zone_gap); omit to leave unchanged
nameYesZone set name, e.g. 'coding'
zonesYes
screenNoMonitor index to assign this set to (0 = primary)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.3
    • addedInput schema / properties / zones / items / properties / name
      Added value: +{
+  "description": "What the zone is called, e.g. 'chat': drawn under its number, spoken to, and accepted by snap_window instead of the number. Unique within the set",
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed5 schema fields changedv0.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / gap
      Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "This set's own gap in points; null follows the default gap (get_state.zone_gap); omit to leave unchanged"
+}
    • addedInput schema / properties / screen / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / screen / minimum
      Added value: +-9007199254740991
    • removedInput schema / properties / zones / items / additionalProperties
      Removed value: -false
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden, and it does so thoroughly. It discloses mutation semantics ('create or replace'), overlap resolution ('smallest one under the cursor wins'), naming uniqueness rules, active assignment via screen, and the nuanced gap behavior when omitting vs passing null.

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 dense but every sentence carries meaning, and the most important purpose is front-loaded. It flows logically from zone definition to naming rules to optional active assignment and gap semantics, ending with a helpful note about built-in sets.

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

Completeness5/5

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

The description gives an agent everything needed to call the tool correctly: required and optional parameters, coordinate semantics, overlap priority, naming constraints, screen activation, gap behavior, and existing built-in sets. There is no output schema, but for a mutation tool the side effects and constraints are thoroughly documented.

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

Parameters5/5

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

Schema coverage is 75%, but the description adds substantial meaning beyond it: zone coordinates are fractions of visible area, origin is top-left, zones must stay inside the screen, names are drawn/spoken/used by snap_window, and gap omission versus null has different outcomes. This lets an agent understand the parameters without needing to infer from the schema alone.

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 opens with 'Create or replace a named zone set used for drag snapping,' giving a specific verb, resource, and domain. It further clarifies what zones are, how they behave, and distinguishes the tool from layout/workspace siblings by focusing on zone sets.

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 description gives clear context for when to use this tool: creating or replacing a named zone set scrape and optionally assigning it to a screen. However, it does not explicitly name alternatives such as assign_zone_set for assigning an existing set without replacement, so some usage-boundary inference is left to the agent.

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