Skip to main content
Glama
muend

arcgis-mcp-bridge

by muend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_to_geojson

Export features to a WGS84 GeoJSON file to share vector data with web maps, APIs, notebooks, and non-Esri tools.

Instructions

Export features to a WGS84 GeoJSON file using ArcPy FeaturesToJSON. Use this to share vector data with web maps, APIs, notebooks, or non-Esri tools. Reads in_features and writes an output .geojson file inside PathGuard allowed roots; existing files require overwrite=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.1
    • addedInput schema / $defs / ExportToGeojsonInput / description
      Added value: +"Export features to a GeoJSON file in WGS84."
    • addedInput schema / $defs / ExportToGeojsonInput / properties / in_features / description
      Added value: +"Absolute path to the input feature class or layer to export as GeoJSON. The path must be inside a configured PathGuard allowed root."
    • changedInput schema / $defs / ExportToGeojsonInput / properties / out_json / description
      Previous value: -"Output .geojson path."New value: +"Absolute output .geojson file path to create. Existing files require overwrite=true."
    • addedInput schema / $defs / ExportToGeojsonInput / properties / overwrite / description
      Added value: +"Set true only when replacing an existing GeoJSON file is intended."
  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 bears the full burden. It describes the read-write process, PathGuard restriction, and overwrite requirement. However, it does not specify whether the tool reprojects to WGS84 or preserves the input projection, nor does it mention selection behavior or attribute handling. Some important behavioral details are missing.

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 extremely concise: three sentences that front-load the main action, then provide usage context and key constraints. Every sentence serves a purpose without redundancy.

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 existence of an output schema (which presumably documents the return structure), the description covers input, output, overwrite, and path restrictions. It lacks explicit mention of coordinate transformation or attribute inclusion, but overall it is fairly complete for a straightforward export 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 already provides descriptions for each parameter. The tool description adds little beyond, explaining the overall process (reading in_features, writing out_json) and the overwrite condition. Since schema coverage is effectively high (despite context claiming 0%), the description provides marginal added value.

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 exports features to a WGS84 GeoJSON file, specifies the underlying tool (ArcPy FeaturesToJSON), and provides usage context for sharing with web maps, APIs, etc. It differentiates from siblings like export_to_shapefile and import_from_geojson.

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 advises when to use the tool ('share vector data with web maps, APIs, notebooks, or non-Esri tools') but does not explicitly mention when not to use it or compare with alternative export tools. Still, the context is clear enough for selection.

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