No user-submitted related servers found.
Scored across 28 tools
Most tools map to clearly distinct operations, and the descriptions explicitly fence off near-neighbors like merge vs. dissolve or validate vs. execute. The main ambiguity is run_operation, which can execute any catalog operation including those with dedicated tools, so an agent must decide between a direct tool and the generic dispatcher.
The dominant convention is verb_noun (merge_layers, buffer_layer, validate_plan, describe_dataset), which is predictable and readable. A minority of terrain/raster tools use noun-only names (slope, aspect, watershed, hillshade, flow_accumulation), creating a minor but recognizable deviation from the pattern.
At 28 tools, this set is heavier than the ideal range for agent selection, even though the broad GIS scope makes the count defensible. The list_operations/run_operation pair helps manage the long tail, but the number of direct tools plus the generic dispatcher adds selection overhead.
The exposed surface covers vector operations, raster/terrain analysis, SQL, inspection, visualization, provenance, and multi-step planning with validation and execution. The list_operations/run_operation bridge makes the wider catalog reachable, so obvious gaps like lineage are accessible without leaving dead ends.