Skip to main content
Glama

Krita Clear Selection

krita_clear_selection

Deselect all active areas in Krita to clear the current selection. Use this to reset your editing scope and continue working without selection boundaries.

Instructions

Deselect everything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Deselect everything' states the primary effect, but does not mention whether it is non-destructive to pixels/layers, what happens if no selection exists, or whether it only affects the current document. The statement is adequate but minimal.

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 extremely concise: two words ('Deselect everything.') with no filler. Every word contributes to the meaning, and the operation is front-loaded and immediately understandable.

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 zero-parameter tool with an output schema, the description is nearly complete: it tells the agent exactly what the tool does. A small gap is that it does not explicitly state that it operates on the current Krita document's active selection, but the tool name and simplicity make this low risk.

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

Parameters4/5

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

The tool has zero parameters, so the input schema already fully describes the invocation surface. The description does not need to elaborate on parameters, and the baseline of 4 for zero-parameter tools applies here.

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

Purpose4/5

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

The description uses a clear verb and object: 'Deselect everything.' It accurately conveys that the tool clears the current selection. It does not explicitly differentiate from sibling selection tools like krita_modify_selection or ase_deselect, but the Krita-specific naming and the operation are unambiguous enough.

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 description gives no guidance on when to use this tool versus alternatives, nor any exclusions or conditions. The only context is the tool's name and title, which imply Krita-specific usage. An agent must infer when clearing a selection is appropriate.

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