Skip to main content
Glama
Sign In
GIS MCP Server

GIS MCP Server

by mahdin75
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

dissolve_gpd

Dissolve geospatial polygons into larger regions by merging those with identical attribute values, simplifying geometry while maintaining data integrity.

Instructions

Dissolve geometries by attribute using geopandas.dissolve. Args: gdf_path: Path to the geospatial file. by: Column to dissolve by (optional). output_path: Optional path to save the result. Returns: Dictionary with status, message, and output info.

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": {
      "gdf_path": "<gdf_path>"
    },
    "name": "dissolve_gpd"
  }
}

Input Schema

NameRequiredDescriptionDefault
gdf_pathYes
byNo
output_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.0.0
    • addedInput schema / properties / by / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / by / title
      Removed value: -"By"
    • removedInput schema / properties / by / type
      Removed value: -"string"
    • removedInput schema / properties / gdf_path / title
      Removed value: -"Gdf Path"
    • addedInput schema / properties / output_path / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / output_path / title
      Removed value: -"Output Path"
    • removedInput schema / properties / output_path / type
      Removed value: -"string"
    • removedInput schema / title
      Removed value: -"dissolve_gpdArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  2. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions an optional output path for saving, but does not disclose whether the operation modifies the input file or other side effects. The return format is described, but behavioral traits like required permissions or error handling are omitted.

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?

The description is concise: a one-sentence summary followed by a structured arg list. It is front-loaded and avoids unnecessary details.

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?

The tool has 3 parameters, all explained. An output schema exists, so the return description is sufficient. However, it lacks context on prerequisites (e.g., file must exist) and error handling, which would be helpful for a geospatial operation.

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?

The description includes a brief arg list explaining each parameter (e.g., 'gdf_path: Path to the geospatial file'), which adds meaning beyond the schema's types. Given 0% schema description coverage, this compensates well.

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?

The description clearly states 'Dissolve geometries by attribute using geopandas.dissolve', which is a specific verb+resource. However, it does not explicitly differentiate from sibling tools like 'merge_gpd' or 'unary_union_geometries', but the operation is distinct enough.

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 is provided on when to use this tool versus alternatives. The description simply states what the tool does without mentioning prerequisites or appropriate use cases.

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