Skip to main content
Glama
Knight60

ArcGIS Pro MCP

by Knight60
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_field_statistics

Calculate min, max, mean, median, sum, and standard deviation for a numeric field in an ArcGIS Pro layer, optionally filtering records with a SQL where clause.

Instructions

min / max / mean / median / sum / standard deviation of a numeric field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldYesField name.
whereNoSQL where clause.
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. Changed4 schema fields changedv1.1.1
    • addedInput schema / properties / field / description
      Added value: +"Field name."
    • 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 / where
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "SQL where clause.",
+  "title": "Where"
+}
  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, and it discloses nothing beyond the computed values. It does not say whether the operation is read-only, whether the 'where' clause restricts the population, or how it interacts with the current selection.

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 fragment with zero filler, and the computed statistics lead the sentence. It is efficient, though terse to the point where the brevity contributes to the missing behavioral context.

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, so return values need not be explained, and the schema documents all four parameters. However, for a tool with no annotations and several close siblings, the description omits the filtering semantics and routing context an agent needs to call it confidently.

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 layer_name, field, where, and map_name are already documented in the schema; baseline 3 applies. The description adds no syntax or format detail beyond that, but nothing is missing that the schema doesn't cover.

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 names a specific resource (a numeric field) and enumerates exactly what is computed (min/max/mean/median/sum/stddev), so an agent knows the output shape without opening the schema. It does not differentiate itself from similar siblings such as summarize_features or get_unique_values, which keeps it short of a 5.

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?

There is no when-to-use guidance at all. With siblings like summarize_features, zonal_statistics, and get_unique_values in the same family, the description never states which conditions select this tool over those alternatives.

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