Skip to main content
Glama
Sign In
GIS Assistant MCP

GIS Assistant MCP

by mfstone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

gis.run

Plan and execute a validated QGIS workflow from a natural-language prompt, returning clarification questions or a resume token when confirmation is needed.

Instructions

Plan AND execute a GIS workflow from a natural-language prompt.

Steps: gather QGIS context -> generate plan -> validate -> execute.

If the plan needs clarification, returns the questions (no execution).
If a confirm step is reached, returns a blocked report with a
resume_token -- use gis.resume() to continue.

Input Schema

NameRequiredDescriptionDefault
promptYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses pipeline stages and conditional outcomes, including no execution on clarification and a blocked report with resume_token on confirmation. It omits side effects or destructive potential of 'execute', permissions, and what a GIS workflow may modify in the QGIS context.

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?

Front-loads 'Plan AND execute a GIS workflow from a natural-language prompt' and then uses a compact step list plus conditional outcomes. Every sentence contributes; there is no filler.

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?

This is a complex orchestrator with an output schema, and the description explains the main flow and branch outcomes. With no annotations, however, it should also cover side effects, prerequisites, and how it relates to sibling planning tools. Return values are adequately supported by the output schema.

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?

The schema has 0% description coverage for the single required prompt parameter. The description adds that the prompt is natural-language, but gives no examples, scope, or constraints. This partially compensates for the schema gap but leaves parameter semantics thin.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: plan AND execute a GIS workflow from a natural-language prompt. The step sequence makes clear it is an end-to-end orchestrator. It only partially distinguishes from siblings, since it names gis.resume for continuation but does not explicitly contrast with gis.plan or gis.run_plan.

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?

Describes the workflow and branch behavior: clarification returns questions without execution, and a confirm step returns a blocked report with a resume_token for gis.resume. However, it does not say when to choose this tool over gis.plan or gis.run_plan for plan-only or execute-only scenarios. Selection guidance is implied by 'Plan AND execute' rather than explicitly stated.

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