Skip to main content
Glama
Sign In
QGIS MCP Server

QGIS MCP Server

by LuiccianDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Commit Edits

commit_edits

Save a layer's pending edits to its data source and close the edit session, finalizing changes made during an editing session in QGIS.

Instructions

Commit the layer's edit buffer to the data source and close the edit session.

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": "commit_edits"
  }
}

Input Schema

NameRequiredDescriptionDefault
layer_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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. It discloses two key behaviors: committing the edit buffer and closing the edit session. However, it does not mention irreversibility, active-session requirements, or error handling, which are important 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?

A single, front-loaded sentence that communicates the action and consequence without waste. Perfectly concise for a simple 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 one-parameter tool with no output schema, the description covers the core behavior and side effect (close edit session). It implicitly assumes an active edit session, which is reasonable given the sibling tools. Minor lack of error-case details is acceptable for this simplicity.

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?

The schema has only layer_id (string) with 0% coverage from the description. The description references 'the layer's' which implies layer_id identifies the target layer, but it doesn't explicitly map the parameter or explain format/requirements. It adds some semantic value but could be clearer.

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 the specific verb 'commit' and identifies the resource ('layer's edit buffer') along with a side effect ('close the edit session'). This clearly distinguishes it from sibling tools like rollback_edits or start_editing.

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 description implies usage as the final step in an editing workflow, but it does not explicitly state when to use this tool versus alternatives like rollback_edits or undo_edits. No exclusions or prerequisites are mentioned.

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