Skip to main content
Glama
Sign In
QGIS MCP Server

QGIS MCP Server

by awheeler262
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Zoom to Layer

zoom_to_layer
Idempotent

Zoom the QGIS map canvas to the full extent of a specified layer, enabling focused navigation to that layer's geographic area.

Instructions

Zoom the map canvas to the full extent of the specified 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": "zoom_to_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
layer_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotation declares idempotentHint=true, so the tool is safe to call repeatedly. Description does not add further behavioral details (e.g., what happens if layer is not found, if it changes state beyond canvas). Neutral impact given annotations.

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, no wasted words. Front-loaded with action and target. Appropriate length for a straightforward tool.

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?

Tool is simple with one parameter and no output schema. Description covers the basic purpose but lacks detail on parameter format and error handling. Acceptable for minimum viability but not fully informative.

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?

Input schema has no descriptions for layer_id (0% coverage). Description only says 'specified layer' without clarifying whether layer_id is a layer name, ID, or how to obtain it. Does not compensate for schema deficiency.

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 clearly states the action (zoom) and target (map canvas to full extent of specified layer). Distinguishes from sibling set_canvas_extent which zooms to arbitrary coordinates.

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?

Description implies usage context (when you want to zoom to layer's extent) but does not explicitly state when not to use it or provide comparison to alternatives like set_canvas_extent. No exclusion criteria or prerequisites 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