Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Delete pattern pieces

clo_delete_patterns
Destructive

Delete pattern pieces and their seams permanently, then re-read scene indices because remaining pieces are renumbered.

Instructions

Delete pattern pieces, along with their seams. Cannot be undone. Remaining pieces are renumbered, so re-read indices with clo_get_scene afterwards.

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": {
      "pattern_indices": "<pattern_indices>"
    },
    "name": "clo_delete_patterns"
  }
}

Input Schema

NameRequiredDescriptionDefault
pattern_indicesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, but the description adds real behavioral context beyond them: seams are deleted with the pieces, the operation is irreversible, and remaining pieces are renumbered. That renumbering side effect is the standout disclosure an agent could not infer from annotations or schema.

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, no waste, with the destructive scope front-loaded and the irreversibility warning and follow-up action ordered by importance.

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 destructive tool with no output schema, the description covers consequences, irreversibility, and the required follow-up read. The remaining gap is parameter-level detail (array form, zero-based indexing) that the schema leaves undocumented.

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

Parameters2/5

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

Schema description coverage is 0% for the top-level parameter; the only hint in the description is the loose word "indices" in the follow-up sentence. It does not explain that pattern_indices is a required array of zero-based integers or that multiple pieces can be deleted in one call, so a low-coverage schema is largely uncompensated.

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 ("Delete pattern pieces") plus the scope of that deletion ("along with their seams"), which is exactly the detail an agent needs to know this is a cascading delete rather than a detach.

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?

Gives a valuable post-call directive ("re-read indices with clo_get_scene afterwards") naming a sibling, but offers no explicit when-to-use guidance versus other mutation tools such as clo_edit_pattern, and no preconditions. Usage is only implied.

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