Skip to main content
Glama
muend

arcgis-mcp-bridge

by muend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

clip_raster

Clip raster datasets to a study area using rectangle, template extent, or polygon geometry. Crop imagery, DEMs, or classified rasters without Spatial Analyst.

Instructions

Clip a raster by rectangle, template extent, or template polygon geometry using ArcPy management Clip. Use this to crop imagery, DEMs, or classified rasters to a study area without requiring Spatial Analyst. Reads in_raster and optional template_dataset and writes out_raster inside PathGuard roots.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.0.1
    • changedInput schema / $defs / ClipRasterInput / description
      Previous value: -"Clip by explicit rectangle and/or template dataset geometry."New value: +"Input contract for clipping a raster by rectangle or template dataset."
    • addedInput schema / $defs / ClipRasterInput / properties / in_raster / description
      Added value: +"Absolute path to the existing input raster dataset. The path must be inside a configured PathGuard allowed root."
    • addedInput schema / $defs / ClipRasterInput / properties / nodata_value / description
      Added value: +"Optional NoData value assigned outside the clipping area where ArcPy supports it."
    • addedInput schema / $defs / ClipRasterInput / properties / out_raster / description
      Added value: +"Absolute output raster path to create. The path must be inside a configured PathGuard allowed root; existing outputs require overwrite=true."
    • addedInput schema / $defs / ClipRasterInput / properties / overwrite / description
      Added value: +"Set true only when replacing an existing output raster is intended."
    • changedInput schema / $defs / ClipRasterInput / properties / template_dataset / description
      Previous value: -"FC/raster whose extent (or geometry) clips."New value: +"Optional feature class or raster whose extent, or polygon geometry when use_clipping_geometry=true, defines the clipping area."
    • changedInput schema / $defs / ClipRasterInput / properties / use_clipping_geometry / description
      Previous value: -"Clip to template polygon geometry, not extent."New value: +"When true, clip to the template polygon geometry instead of only the template extent. Requires template_dataset."
    • addedInput schema / $defs / ClipRasterInput / properties / xmax / description
      Added value: +"Maximum X coordinate of the clipping rectangle. Must be greater than xmin when rectangle clipping is used."
    • addedInput schema / $defs / ClipRasterInput / properties / xmin / description
      Added value: +"Minimum X coordinate of the clipping rectangle. Provide all four rectangle bounds together, or leave all bounds None and use template_dataset."
    • addedInput schema / $defs / ClipRasterInput / properties / ymax / description
      Added value: +"Maximum Y coordinate of the clipping rectangle. Must be greater than ymin when rectangle clipping is used."
    • addedInput schema / $defs / ClipRasterInput / properties / ymin / description
      Added value: +"Minimum Y coordinate of the clipping rectangle. Provide all four rectangle bounds together, or leave all bounds None and use template_dataset."
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Mentions reading input and writing output inside PathGuard roots, but does not disclose potential side effects like overwriting, permissions needed, or how existing data is handled. The overwrite parameter is mentioned in schema but not in description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action. Efficiently covers primary use and constraints. Could be slightly more structured but is concise and informative.

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?

Covers main functionality, inputs, output constraints, and use cases. Does not detail error handling or edge cases, but sufficient for an agent to understand when to invoke this tool correctly.

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?

Schema already provides detailed parameter descriptions. The tool description adds context about the three clipping methods (rectangle, extent, polygon) which relate to parameters, but does not explain each parameter individually. PathGuard constraint is mentioned, which adds value beyond schema.

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?

Description clearly states action 'Clip', resource 'raster', and specifies three methods: rectangle, template extent, polygon. It differentiates from siblings like extract_by_mask by mentioning it uses ArcPy management Clip and does not require Spatial Analyst.

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?

Provides explicit context for use: 'crop imagery, DEMs, or classified rasters to a study area without requiring Spatial Analyst.' Does not explicitly state when not to use or contrast with alternatives, but gives clear guidance.

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