Skip to main content
Glama
Sign In
krita6-mcp

krita6-mcp

by fanzhuyifan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

krita_list_diffusion_styles

Read-onlyIdempotent

Lists available AI Diffusion styles and their handles without altering the current style, helping you identify options before selecting one.

Instructions

List available AI Diffusion styles and their handles without changing the current style.

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>"
    },
    "name": "krita_list_diffusion_styles"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds a concrete behavioral guarantee—'without changing the current style'—which is useful for an agent deciding whether to call this tool before configuring diffusion.

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?

One sentence, front-loaded with the action and resource, with no filler or repetition. Every word contributes useful meaning.

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 read-only listing tool, the description covers what is returned (styles and handles) and the side-effect guarantee. It does not detail the output format, but no output schema exists and the scope is small; the only real gap is the unmentioned instance_id parameter.

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%, and the description does not explain the required instance_id parameter at all. The schema's title and regex pattern provide some meaning, but the description was expected to compensate for the low schema coverage and does not.

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 states a specific verb ('List'), a specific resource ('available AI Diffusion styles and their handles'), and explicitly notes it does not change the current style. This clearly distinguishes it from mutation-style sibling tools like krita_set_diffusion_controls or krita_configure_diffusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'without changing the current style' gives clear context that this is for inspection and selection exploration, not for applying a style. It does not explicitly name alternatives or state when not to use it, but the non-mutating framing makes the appropriate usage obvious.

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