Skip to main content
Glama
muend

arcgis-mcp-bridge

by muend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calculate_geometry

Calculate area, length, perimeter, centroid, or point coordinates and store them in an attribute field for reporting, QA/QC, or analysis.

Instructions

Calculate area, length, perimeter, centroid, or point coordinate values into an attribute field using ArcPy CalculateGeometryAttributes. Use this to populate measurement fields for reporting, QA/QC, labeling, or downstream analysis. Mutates the input dataset by writing geometry values into the specified field.

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 changedv1.0.1
    • addedInput schema / $defs / CalculateGeometryInput / description
      Added value: +"Calculate area, length, perimeter, centroid, or point coordinate attributes."
    • changedInput schema / $defs / CalculateGeometryInput / properties / area_unit / description
      Previous value: -"e.g. SQUARE_METERS"New value: +"Optional area unit for area calculations, for example SQUARE_METERS. Ignored for non-area geometry properties."
    • changedInput schema / $defs / CalculateGeometryInput / properties / dataset / description
      Previous value: -"Absolute dataset path."New value: +"Absolute path to an existing feature class, table, raster, or geodatabase item. The path must be inside a configured PathGuard allowed root."
    • addedInput schema / $defs / CalculateGeometryInput / properties / field_name / description
      Added value: +"Existing or target field name that will receive the calculated geometry value."
    • addedInput schema / $defs / CalculateGeometryInput / properties / geometry_property / description
      Added value: +"Geometry property to calculate, such as AREA, LENGTH, CENTROID_X, CENTROID_Y, POINT_X, or POINT_Y."
    • changedInput schema / $defs / CalculateGeometryInput / properties / length_unit / description
      Previous value: -"e.g. METERS"New value: +"Optional length unit for length or perimeter calculations, for example METERS. Ignored for non-length geometry properties."
  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 carries the burden. It declares mutation and lists supported geometry properties, but does not clarify if the field is created automatically or if values are overwritten. Missing details like prerequisites or field creation behavior.

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?

Two sentences, no wasted words. First sentence front-loads the core purpose, second adds usage context and mutation warning. Excellent conciseness.

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 presence of an output schema (not shown) and comprehensive input schema descriptions, the tool description covers the essentials: purpose, usage, and mutation. Could mention the lack of return value but is adequate for a mutation tool.

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 includes full descriptions for each property, so the baseline is 3. The description adds context by listing geometry property options and mentioning ArcPy, but does not explain unit parameters or path constraints beyond what 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 the tool calculates geometry properties (area, length, perimeter, centroid, point coordinates) into an attribute field using ArcPy. It distinguishes from siblings like calculate_field and add_xy_coordinates by specifying the exact geometry calculations.

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 explicit use cases (reporting, QA/QC, labeling, downstream analysis) and mentions mutation. However, it does not explicitly state when NOT to use this tool or suggest alternatives like calculate_field for non-geometry calculations.

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