Skip to main content
Glama
Sign In
QGIS MCP

QGIS MCP

by lefcgis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Canvas Screenshot

get_canvas_screenshot
Read-only

Take a screenshot of the current map canvas without re-rendering. Returns the image inline.

Instructions

Grab a fast screenshot of the current map canvas widget (no re-render). Returns the image inline. Much faster than render_map.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_canvas_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint true, so safety is covered. The description adds behavioral details: no re-render, fast, returns inline image, which is consistent with annotations. It does not disclose potential limitations such as format or resolution, but given the low risk, it's adequate.

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?

Two concise sentences with no unnecessary words. The key points (fast, no re-render, inline return, faster than render_map) are front-loaded and immediately actionable.

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 simple tool with no parameters and clear annotations, the description covers essential context. It mentions the return type and performance benefit. Could specify image format, but not critical for selection.

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?

With zero parameters and 100% schema description coverage, the baseline is 4. The description adds no parameter specifics because none exist, but this is appropriate.

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 it grabs a fast screenshot of the current map canvas widget without re-render, and distinguishes itself from render_map by noting it is much faster. This effectively differentiates it from siblings like get_3d_screenshot and render_map.

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 implies usage when a fast screenshot without re-render is needed, and contrasts with render_map by highlighting speed. However, it does not explicitly exclude scenarios where a full render is required, but the context is clear enough.

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