arcgis-mcp-bridge

Overview Schema Source Related Servers Discussions Admin

hillshade

Create shaded relief from elevation rasters for terrain visualization and DEM quality control using controlled sun azimuth, altitude, and shadow modeling.

Instructions

Create shaded relief from an elevation raster using ArcPy Spatial Analyst Hillshade. Use this for terrain visualization, map backdrops, and DEM QA/QC with controlled sun azimuth, altitude, shadow modeling, and z_factor. Requires a Spatial Analyst license.

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.

Changed8 schema fields changedv1.0.1Jul 4, 2026

addedInput schema / $defs / HillshadeInput / description

Added value: +"Input contract for deriving shaded relief from an elevation raster."

addedInput schema / $defs / HillshadeInput / properties / altitude / description

Added value: +"Illumination altitude angle in degrees above the horizon. Higher values create more overhead lighting."

addedInput schema / $defs / HillshadeInput / properties / azimuth / description

Added value: +"Illumination azimuth in degrees clockwise from north. The default 315 degrees represents northwest light."

addedInput schema / $defs / HillshadeInput / 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 / HillshadeInput / properties / model_shadows / description

Added value: +"When true, model terrain shadows where supported by ArcPy hillshade."

addedInput schema / $defs / HillshadeInput / 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 / HillshadeInput / properties / overwrite / description

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

changedInput schema / $defs / HillshadeInput / properties / z_factor / description

Previous value: -"Vertical unit conversion (e.g. 0.3048 if Z is in feet and XY in meters)."New value: +"Vertical unit conversion or exaggeration factor. Use 1.0 when XY and Z units already match; for example use 0.3048 when elevation Z values are in feet and XY units are meters."

First observedv1.0.0Jul 4, 2026

TDQS

A3.9/5.0

Behavior3/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 notes the use of ArcPy Spatial Analyst and license requirement, but does not detail behaviors like input validation, performance, or what happens on overwrite. The parameter descriptions in the schema cover some aspects, but the tool description lacks deeper behavioral 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 long, with the first sentence stating the core purpose and the second adding use cases and the license requirement. No extraneous words.

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, return values are covered. The description explains what the tool does, when to use it, and a prerequisite (license). It omits details like prerequisite input conditions or potential errors, but overall it is sufficiently informative for a raster tool with well-documented parameters.

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%, yet the description adds no new meaning beyond listing 'controlled sun azimuth, altitude, shadow modeling, and z_factor.' All parameter details are already in the schema, so the description provides minimal added value for parameter understanding.

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 starts with 'Create shaded relief from an elevation raster using ArcPy Spatial Analyst Hillshade,' which is a specific verb+resource. It clearly states the tool's output and distinguishes it from siblings like slope_analysis or aspect_analysis by focusing on hillshade.

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 specifies use cases: 'terrain visualization, map backdrops, and DEM QA/QC' and mentions the required license. However, it does not explicitly exclude other uses or contrast with alternatives.

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

Deploy Server