QGIS MCP Server

Get Message Log

get_message_log

Read-only

Retrieve QGIS message log entries filtered by severity level or tag, returning the newest entries first for debugging and monitoring.

Instructions

Get QGIS message log entries. Filter by level ('info', 'warning', 'critical', 'success', 'none') and/or tag (e.g. 'QGIS MCP'). Returns newest first.

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_message_log"
  }
}

Input Schema

Name	Required	Description	Default
`tag`	No
`level`	No
`limit`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses that results are returned newest-first and enumerates the valid level values ('info', 'warning', 'critical', 'success', 'none'). This gives the agent meaningful behavioral detail beyond the annotation alone.

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 short sentences front-load the core purpose, immediately follow with filter options, and close with ordering behavior. Every clause contributes value with no wasted wording.

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?

With a readOnlyHint, an output schema, and only three optional parameters, the description covers the essential behaviors: what is retrieved, how to filter, valid level values, and result ordering. The only minor gap is the lack of any explanation of the 'limit' parameter's semantics or interaction with the other filters.

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?

With 0% schema description coverage, the description compensates for 'level' and 'tag' by listing valid values and giving an example. However, the 'limit' parameter is not mentioned at all, leaving its meaning and default behavior undocumented outside the schema.

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?

States a specific verb ('Get') and resource ('QGIS message log entries'), and further clarifies the scope with filtering by level/tag. This unambiguously distinguishes it from the many sibling tools, none of which target message log access.

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 makes clear this tool is for retrieving message log entries and describes the available filters. It does not explicitly name an alternative or a when-not-to-use case, but no sibling tool obviously overlaps with this function.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server