Skip to main content
Glama
Sign In
QGIS MCP

QGIS MCP

by lefcgis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Add Bookmark

add_bookmark

Save a map view as a bookmark in QGIS by providing a name, bounding box coordinates (xmin, ymin, xmax, ymax), and coordinate reference system.

Instructions

Add a spatial bookmark to the project for quick navigation. Provide a name and extent (xmin/ymin/xmax/ymax) with CRS.

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": {
      "name": "<name>",
      "xmin": "<xmin>",
      "ymin": "<ymin>",
      "xmax": "<xmax>",
      "ymax": "<ymax>"
    },
    "name": "add_bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
crsNoEPSG:4326
nameYes
xmaxYes
xminYes
ymaxYes
yminYes
groupNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.6/5.0
Behavior2/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 mentions adding a bookmark but does not disclose behavioral traits such as whether duplicate names are allowed, CRS validation, or effects on existing bookmarks.

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, clear sentence that front-loads the action and key inputs with no unnecessary words.

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?

Given no output schema and no annotations, the description is minimally adequate for a simple create operation but lacks completeness: it does not specify return values, success/failure indications, or error conditions.

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?

The description mentions name, extent parameters (xmin, ymin, xmax, ymax), and CRS, but omits the optional 'group' parameter entirely. With 0% schema description coverage, the description fails to compensate by providing additional meaning or format guidance for the parameters.

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 uses a specific verb ('Add') and resource ('spatial bookmark'), and clearly states the tool's purpose for quick navigation. It distinguishes from siblings like 'get_bookmarks' (list) and 'remove_bookmark' (delete).

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 description implicitly indicates usage for adding a bookmark but provides no explicit guidance on when to use alternatives or when not to use. However, the sibling tools have distinct operations, making the context clear.

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