Skip to main content
Glama
Sign In
QGIS MCP Server

QGIS MCP Server

by LuiccianDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Redo Edits

redo_edits

Reapply previously undone edit operations on a QGIS layer, optionally for multiple steps, to restore changes after an undo.

Instructions

Redo previously undone edit operations on a layer.

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

Input Schema

NameRequiredDescriptionDefault
stepsNo
layer_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It states the operation type (redo) but omits important behavioral details like what happens if there are no undone edits, whether an edit session is required, or whether the operation is reversible. This is a significant gap for a mutation tool.

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?

Single sentence, front-loaded, no wasted words. It efficiently conveys the core action and target, though it is minimal in content.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks context about when redo is applicable, how the 'steps' parameter works, and potential error conditions, making it insufficient for an agent to invoke confidently.

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 mention layer_id or steps. The 'steps' parameter is ambiguous—its meaning as a count of undo steps is only inferable from the name, not from the description, which says 'operations' but does not clarify the parameter.

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?

Description uses specific verb 'Redo' and resource 'previously undone edit operations on a layer', clearly distinguishing from sibling 'undo_edits'. It is more than just a restatement of the title.

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?

The phrase 'previously undone' implies usage after an undo, but it does not explicitly state when to use this vs alternatives like undo_edits, nor does it mention prerequisites such as being in an active editing session. Guidance is implied rather than explicit.

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