Skip to main content
Glama
muend

arcgis-mcp-bridge

by muend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_fields_batch

Add multiple fields to an existing feature class or table in a single operation using ArcPy, enabling quick schema preparation for data imports, calculations, or QA/QC.

Instructions

Add multiple fields to an existing feature class or table in one operation using ArcPy AddFields. Use this to prepare a complete attribute schema before imports, calculations, joins, or QA/QC. Mutates the input dataset schema; field names, types, aliases, and lengths are validated before execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.0.1
    • addedInput schema / $defs / AddFieldsBatchInput / description
      Added value: +"Add multiple fields to an existing table or feature class."
    • changedInput schema / $defs / AddFieldsBatchInput / 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 / AddFieldsBatchInput / properties / fields / description
      Added value: +"Field definitions to add in one ArcPy AddFields operation. Each definition includes a name, type, optional alias, and optional length."
    • changedInput schema / $defs / FieldDef / description
      Previous value: -"One field for the batch AddFields call."New value: +"One field definition for the batch AddFields call."
    • addedInput schema / $defs / FieldDef / properties / alias / description
      Added value: +"Optional human-readable field alias shown in ArcGIS."
    • addedInput schema / $defs / FieldDef / properties / length / description
      Added value: +"Optional text field length. Primarily used when type is TEXT."
    • addedInput schema / $defs / FieldDef / properties / name / description
      Added value: +"Name of the field to add. Use a valid ArcGIS field name beginning with a letter or underscore."
    • addedInput schema / $defs / FieldDef / properties / type / description
      Added value: +"ArcGIS field type to create, such as TEXT, LONG, DOUBLE, or DATE."
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Given no annotations, the description reveals that it mutates the schema and validates field names/types/aliases/lengths. However, it lacks details on error handling, transaction atomicity, or prerequisites like dataset existence.

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 efficient sentences with no redundant information, front-loaded with the core action and use cases.

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?

With an output schema present, return values need not be explained. However, the description omits limits (e.g., max 100 fields) and fails to clarify whether the operation is atomic or partially applied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It fails to mention the 'dataset' and 'fields' parameters or their constraints, leaving agents to infer from the schema alone.

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 verb 'Add multiple fields' and the resource 'existing feature class or table', distinguishing it from the sibling tool 'add_field' by emphasizing the batch operation.

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 explicitly recommends use for 'before imports, calculations, joins, or QA/QC', providing clear context. It doesn't explicitly state when not to use it, but the batch vs single field distinction is implicit.

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