Skip to main content
Glama
Sign In
krita6-mcp

krita6-mcp

by fanzhuyifan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

krita_set_selection

DestructiveIdempotent

Set or modify a document selection by replacing, adding, subtracting, or intersecting with a rectangle or polygon defined in pixel coordinates.

Instructions

Replace or combine the selection with a bounded rectangle or polygon in image pixels. Rectangle requires only x/y/width/height; polygon requires only 3–256 integer points. Selection bounds must fit the canvas and 16 megapixels. No guaranteed undo transaction.

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": {
      "instance_id": "<instance_id>",
      "operation_id": "<operation_id>",
      "document_id": "<document_id>",
      "shape": "<shape>"
    },
    "name": "krita_set_selection"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
modeNoreplace
shapeYes
widthNo
heightNo
pointsNo
document_idYes
instance_idYes
operation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already mark destructiveHint=true and readOnlyHint=false. The description adds the important caveat 'No guaranteed undo transaction' and the canvas/16MP bounds constraint, giving the agent a clear risk warning beyond the annotations.

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 sentences, each with a distinct purpose: operation, shape-specific requirements, and constraints/warning. No filler or repetition.

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

Completeness3/5

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

The description covers operation, shape conditions, bounds constraints, and undo caveat, but omits the effect of each mode (beyond a vague 'combine'), error behavior when bounds are exceeded, and any operation/return semantics (despite a required operation_id and no output schema). Thus adequate but not 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 0%, so the description must carry parameter semantics. It clarifies that rectangle uses x/y/width/height and polygon uses 3–256 integer points, which is helpful. However, it doesn't explain the mode values (add/subtract/intersect), coordinate system, or how points map to [x,y] pairs, leaving gaps.

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?

States a specific verb ('Replace or combine') and resource ('the selection'), and specifies shapes (rectangle/polygon) and units (image pixels). However, it doesn't explicitly differentiate from sibling krita_modify_selection or mention the mode parameter, leaving some ambiguity about what 'combine' covers.

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?

No guidance on when to use this tool versus the sibling krita_modify_selection or krita_clear_selection. It describes how to specify shapes and constraints, but does not address alternatives or prerequisites such as an active document or how to select a mode.

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