QGIS MCP Server

Set Raster Style

set_raster_style

Set raster symbology in QGIS by choosing pseudocolor, grayscale, RGB, or hillshade styles, with color ramps, classification, and contrast controls.

Instructions

Set raster symbology. style_type: 'singleband_pseudocolor' (color ramp over one band), 'singleband_gray', 'multiband_color' (RGB), 'hillshade'. min_value/max_value default to the band statistics. color_ramp: QGIS ramp name (e.g. 'Viridis', 'Spectral', 'RdYlGn'). classification: continuous|equal_interval|quantile. interpolation: interpolated|discrete|exact. gradient (gray): black_to_white|white_to_black. contrast: none|stretch|clip|stretch_clip. hillshade uses band, azimuth, altitude, z_factor.

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": {
      "layer_id": "<layer_id>",
      "style_type": "<style_type>"
    },
    "name": "set_raster_style"
  }
}

Input Schema

Name	Required	Default
`band`	No
`azimuth`	No
`classes`	No
`altitude`	No
`contrast`	No	stretch
`gradient`	No	black_to_white
`layer_id`	Yes
`red_band`	No
`z_factor`	No
`blue_band`	No
`max_value`	No
`min_value`	No
`color_ramp`	No	Viridis
`green_band`	No
`style_type`	Yes
`interpolation`	No	interpolated
`classification`	No	continuous

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full transparency burden. It discloses meaningful behavior: min_value/max_value default to band statistics, hillshade uses band/azimuth/altitude/z_factor, and lists valid options for classification, interpolation, gradient, and contrast. It doesn't describe return values or persistence, but covers core behavior.

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 a single dense paragraph with no filler. It is front-loaded with the core action and every clause adds valuable parameter or option detail, making it an efficient reference for a 17-parameter tool.

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 complex tool with 17 parameters, no annotations, and no output schema, the description covers most necessary invocation details, including style-type-specific parameter usage. It lacks explicit prerequisites (e.g., the layer must be a raster layer) and alternative-tool context, but the schema's required layer_id and the 'raster symbology' wording make this largely sufficient.

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?

Schema coverage is 0%, so the description compensates by explaining style_type variants, color_ramp examples, and parameter relationships (e.g., hillshade parameters). Some parameters like layer_id, red_band, green_band, blue_band, and classes are not explicitly defined, but they are partially inferable from the RGB and hillshade hints.

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 clearly states 'Set raster symbology' and expands with specific style_type variants ('singleband_pseudocolor', 'singleband_gray', 'multiband_color', 'hillshade'), making it distinct from the broader sibling set_layer_style and apply_style_qml tools.

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?

Usage context is implied by the tool name and 'raster symbology', and the description gives useful style-type choices, but it never explicitly says when to use this tool instead of alternatives like set_layer_style or apply_style_qml, nor does it mention any exclusions.

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

Deploy Server