Skip to main content
Glama
Sign In
QGIS MCP Server

QGIS MCP Server

by awheeler262
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Layout Info

get_layout_info
Read-only

List items in a QGIS print layout with type, ID, UUID, position, size, and page count.

Instructions

List items in a print layout (type, id, uuid, position, size) and page count.

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": {
      "layout_name": "<layout_name>"
    },
    "name": "get_layout_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
layout_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description confirms a read operation (listing items). It does not add behavioral context beyond annotations (e.g., what if layout does not exist). Adequate but no extra value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with no wasted words. However, it could be structured to highlight the parameter or return value. Still efficient.

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 low complexity (1 parameter, output schema exists), the description is partially complete. It lacks parameter explanation but covers the main purpose. Missing details on how to specify the layout name.

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 coverage is 0% and the description does not explain the 'layout_name' parameter. The agent must infer that it is the name of the layout, but no details on format or uniqueness. Description should compensate but does not.

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 lists items in a print layout with specific attributes (type, id, uuid, position, size) and page count. It distinguishes from 'list_layouts' which lists layouts themselves, so it is specific and not a tautology.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. There are sibling tools like 'add_layout_map' or 'export_layout' that relate to layouts, but no explicit context for usage. Minimal hints.

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