Skip to main content
Glama
muend

arcgis-mcp-bridge

by muend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mean_center

Calculate the geographic mean center of input features to summarize central tendency of incidents or locations, with optional weighting and grouping by case field.

Instructions

Calculate the geographic mean center of input features using ArcPy MeanCenter and write the result as a point feature class. Use this to summarize the central tendency of incidents, facilities, parcels, demand points, or grouped spatial observations. Supports optional weight_field and case_field parameters; reads in_features and writes out_features inside PathGuard allowed roots.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.6.3
    • addedInput schema / $defs / MeanCenterInput / description
      Added value: +"Input contract for calculating the geographic mean center of features."
    • addedInput schema / $defs / MeanCenterInput / properties / case_field / description
      Added value: +"Optional field used to group features and calculate one mean center per group. Use None to calculate one mean center for all features."
    • addedInput schema / $defs / MeanCenterInput / properties / in_features / description
      Added value: +"Absolute path to the input feature class used for spatial statistics. The path must be inside a configured PathGuard allowed root."
    • addedInput schema / $defs / MeanCenterInput / properties / out_features / description
      Added value: +"Absolute output feature class path to create with statistical results. The path must be inside a configured PathGuard allowed root; existing outputs require overwrite=true."
    • addedInput schema / $defs / MeanCenterInput / properties / overwrite / description
      Added value: +"Set true only when replacing an existing spatial statistics output feature class is intended."
    • addedInput schema / $defs / MeanCenterInput / properties / weight_field / description
      Added value: +"Optional numeric field used to weight features when calculating the mean center. Use None when every feature should contribute equally."
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It discloses that it writes a point feature class, uses ArcPy MeanCenter, and respects PathGuard allowed roots. However, it does not mention potential side effects like overwriting or performance considerations for large datasets.

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?

The description is two sentences long, front-loaded with the main purpose, and includes essential use cases and parameter hints. Every sentence adds value, and there is no wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (statistical calculation with optional weighting and grouping), the description covers the main points and typical uses. An output schema exists, so return values are documented separately. Could mention that output includes fields for coordinates and groups.

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 input schema provides descriptions for all parameters (100% coverage), so the baseline is 3. The description adds context about PathGuard allowed roots and optional weight/case fields, but does not add significant meaning beyond what the schema already provides.

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

Purpose5/5

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

The description clearly states that the tool calculates the geographic mean center using ArcPy MeanCenter and writes a point feature class. It specifies the resource (mean center) and verb (calculate), and distinguishes from siblings by focusing on central tendency summary for incidents, facilities, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides typical use cases (summarizing central tendency of various spatial features) and mentions optional parameters. However, it does not explicitly state when not to use this tool or suggest alternatives like directional_distribution for dispersion.

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