arcgis-mcp-bridge

Overview Schema Source Related Servers Discussions Admin

import_from_geojson

Convert a GeoJSON file into an ArcGIS feature class for geodatabase analysis. Reads point, line, or polygon data, detects geometry type, and writes output features within allowed paths.

Instructions

Convert a GeoJSON file into an ArcGIS feature class using ArcPy JSONToFeatures. Use this to bring web, API, or exchange-format vector data into a geodatabase for ArcGIS analysis. Reads an input .geojson file, detects its point, line, or polygon geometry type (set geometry_type for mixed files), and writes out_features inside PathGuard allowed roots; existing outputs require overwrite=true.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.6.7Sep 25, 2026

addedInput schema / $defs / ImportFromGeojsonInput / properties / geometry_type

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "POINT",
+        "MULTIPOINT",
+        "POLYLINE",
+        "POLYGON"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Geometry type to import from a .geojson file. Leave unset to detect it from the file's features. Set it when the file mixes geometry types: only features of this type are imported. Not valid for Esri JSON (.json) input, which declares its own geometry type.",
+  "title": "Geometry Type"
+}

Changed4 schema fields changedv1.0.1Jul 4, 2026

addedInput schema / $defs / ImportFromGeojsonInput / description

Added value: +"Convert a GeoJSON file into an ArcGIS feature class."

addedInput schema / $defs / ImportFromGeojsonInput / properties / in_json / description

Added value: +"Absolute path to the input .geojson file to convert. The file must be inside a configured PathGuard allowed root."

addedInput schema / $defs / ImportFromGeojsonInput / properties / out_features / description

Added value: +"Absolute output feature class path to create from the GeoJSON. Existing outputs require overwrite=true."

addedInput schema / $defs / ImportFromGeojsonInput / properties / overwrite / description

Added value: +"Set true only when replacing an existing output feature class is intended."

First observedv1.0.0Jul 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals key behaviors: geometry type auto-detection and the option to force geometry_type for mixed files, the PathGuard allowed-root constraint, and the requirement for overwrite=true when the output exists. These are non-obvious operational details that an agent needs to know before calling. It does not contradict any annotations (none exist) and adds substantial context.

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 with zero filler. The purpose is front-loaded, followed by the primary use case, then key behavioral details (geometry detection, PathGuard, overwrite). Every sentence earns its place, and the structure is logically ordered for quick comprehension.

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?

For a conversion tool with a schema that documents parameters and an output schema (not shown), the description covers the essential behaviors: input format, geometry handling, output location constraints, and overwrite semantics. It does not mention coordinate systems, field mapping, or error handling, but these are typically covered by the output schema and are not critical for basic invocation. Given the presence of a schema and the tool's straightforward nature, the description is sufficiently complete.

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

Parameters4/5

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

The schema already provides detailed descriptions for each parameter (e.g., geometry_type explains detection and mixed-file behavior), so the baseline is 3. The description reinforces and adds slight value by explicitly linking 'set geometry_type for mixed files' to the geometry detection mechanism and restating the PathGuard and overwrite constraints. While not adding entirely new semantics, it reinforces the critical constraints in a single sentence, which is helpful.

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 states a specific verb and resource: 'Convert a GeoJSON file into an ArcGIS feature class using ArcPy JSONToFeatures.' It clearly differentiates from siblings like export_to_geojson by specifying the import direction and the intended use case (bringing web/API/exchange-format data into a geodatabase). This is unambiguous and action-oriented.

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 says 'Use this to bring web, API, or exchange-format vector data into a geodatabase for ArcGIS analysis,' which establishes the primary scenario. It does not explicitly name alternatives or state when not to use it, but the context is clear enough to guide an agent away from export or creation tools. A small deduction for not naming the sibling tool export_to_geojson as the alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server