Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
pingA

Simple ping command to check server connectivity

get_qgis_infoC

Get QGIS information

load_projectB

Load a QGIS project from the specified path.

create_new_projectC

Create a new project a save it

get_project_infoC

Get current project information

add_vector_layerC

Add a vector layer to the project.

add_raster_layerC

Add a raster layer to the project.

get_layersA

Retrieve all layers in the current project.

remove_layerB

Remove a layer from the project by its ID.

zoom_to_layerC

Zoom to the extent of a specified layer.

get_layer_featuresB

Retrieve features from a vector layer with an optional limit.

execute_processingC

Execute a processing algorithm with the given parameters.

save_projectA

Save the current project to the given path, or to the current project path if not specified.

render_mapC

Render the current map view to an image file with the specified dimensions.

execute_codeC

Execute arbitrary PyQGIS code provided as a string.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 15 tools

Disambiguation4/5

Most tools have distinct purposes, such as add_raster_layer vs add_vector_layer, but some overlap exists: get_layers retrieves all layers, while get_layer_features retrieves features from a specific vector layer, which could cause confusion if an agent needs general layer info. However, descriptions clarify their differences, preventing major misselection.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case, such as add_raster_layer, execute_code, and get_project_info. There are no deviations in naming conventions, making the set predictable and easy to parse for agents.

Tool Count5/5

With 15 tools, this server is well-scoped for QGIS operations, covering project management, layer handling, rendering, and code execution. Each tool serves a clear purpose without redundancy, fitting the typical range of 3-15 tools for a focused domain.

Completeness4/5

The tool set provides comprehensive coverage for core QGIS workflows, including project CRUD (create, load, save), layer management (add, remove, zoom), and information retrieval. A minor gap is the lack of tools for editing layer attributes or geometries, but agents can work around this using execute_code or execute_processing for advanced operations.

Maintenance

ActivityInactive
ResponsivenessNo issues