Skip to main content
Glama
Knight60

ArcGIS Pro MCP

by Knight60
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

select_features

Select features by SQL where clause, with options to invert, add, remove, or subset the selection. Defaults to new selection on the active map.

Instructions

Select features by SQL where clause.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
whereYesSQL where clause.
invertNoINVERT to select everything the clause does not match.NON_INVERT
methodNoNEW_SELECTION, ADD_TO_SELECTION, REMOVE_FROM_SELECTION, SUBSET_SELECTION, SWITCH_SELECTION or CLEAR_SELECTION.NEW_SELECTION
map_nameNoMap to act on; defaults to the active map.
layer_nameYesLayer or table name as shown by get_layers, or a full dataset path.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.1.1
    • addedInput schema / properties / invert
      Added value: +{
+  "default": "NON_INVERT",
+  "description": "INVERT to select everything the clause does not match.",
+  "title": "Invert",
+  "type": "string"
+}
    • addedInput schema / properties / layer_name / description
      Added value: +"Layer or table name as shown by get_layers, or a full dataset path."
    • addedInput schema / properties / map_name / description
      Added value: +"Map to act on; defaults to the active map."
    • addedInput schema / properties / method / description
      Added value: +"NEW_SELECTION, ADD_TO_SELECTION, REMOVE_FROM_SELECTION, SUBSET_SELECTION, SWITCH_SELECTION or CLEAR_SELECTION."
    • addedInput schema / properties / where / description
      Added value: +"SQL where clause."
  2. First observedv0.1.0

TDQS

C2.9/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 the full burden. It does not disclose that selection modifies current map selection state, whether an active map is required, or persistence/undo behavior; only the schema method parameter hints at selection modes.

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?

A single front-loaded sentence with no wasted words. However, its extreme brevity for a five-parameter tool with no annotations borders on under-specification rather than optimal conciseness.

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?

An output schema exists and all parameters are fully documented, reducing the description's burden. Yet with no annotations, it omits behavioral and usage context needed to select and invoke the tool confidently alongside siblings.

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?

Schema description coverage is 100%, so the baseline is 3. The description references 'SQL where clause' but adds no syntax, format, or meaning beyond what the schema already documents for each parameter.

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 (select) and resource (features) plus the mechanism (SQL where clause). Distinguishes from spatial sibling select_by_location by mechanism, but does not name alternatives explicitly.

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 when-to-use, prerequisites, or alternatives are provided. The phrase 'by SQL where clause' implies usage but does not guide selection versus select_by_location, set_selection, or clear_selection.

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