Skip to main content
Glama
muend

arcgis-mcp-bridge

by muend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mosaic_to_new_raster

Merge multiple raster tiles, scenes, or DEM sheets into a single raster dataset using ArcPy's MosaicToNewRaster function. Specify output location, pixel type, and mosaic method to combine overlapping cells.

Instructions

Merge multiple raster datasets into one new raster using ArcPy MosaicToNewRaster. Use this to combine tiles, scenes, DEM sheets, or image bands into a single dataset. Reads two or more input rasters and writes a named raster into an existing folder or geodatabase.

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 / MosaicToNewRasterInput / description
      Added value: +"Input contract for mosaicking multiple rasters into a new raster dataset."
    • addedInput schema / $defs / MosaicToNewRasterInput / properties / cell_size / description
      Added value: +"Optional output cell size in map units. Use None to let ArcPy choose from the input rasters."
    • addedInput schema / $defs / MosaicToNewRasterInput / properties / mosaic_method / description
      Added value: +"Method used to resolve overlapping raster cells, such as FIRST, LAST, BLEND, MEAN, MINIMUM, or MAXIMUM."
    • addedInput schema / $defs / MosaicToNewRasterInput / properties / number_of_bands / description
      Added value: +"Number of bands in the output raster dataset."
    • changedInput schema / $defs / MosaicToNewRasterInput / properties / output_location / description
      Previous value: -"Existing folder or GDB."New value: +"Absolute path to an existing folder or geodatabase where the mosaic output raster will be created. Must be inside a configured PathGuard allowed root."
    • addedInput schema / $defs / MosaicToNewRasterInput / properties / pixel_type / description
      Added value: +"Pixel depth and numeric type for the output raster, such as 8_BIT_UNSIGNED, 16_BIT_SIGNED, or 32_BIT_FLOAT."
    • changedInput schema / $defs / MosaicToNewRasterInput / properties / raster_name / description
      Previous value: -"Output name (with .tif etc. if folder)."New value: +"Name of the output raster. Include an extension such as .tif when writing to a folder; use a geodatabase raster name when writing to a GDB."
    • addedInput schema / $defs / MosaicToNewRasterInput / properties / rasters / description
      Added value: +"Absolute paths to two or more input raster datasets to mosaic. Each path must be inside a configured PathGuard allowed root."
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations provided, so description bears full burden. Only states it reads inputs and writes output; lacks information on side effects, overwrite behavior, required permissions, or computational intensity. The mention of ArcPy implies a processing function but is insufficient for safe invocation.

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 concise sentences that front-load the core purpose and action. No redundant phrases; each sentence contributes meaningful information.

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?

Covers basic operation and output location requirement. With an output schema present, return values are documented. Missing prerequisites (spatial reference alignment), overwrite behavior, and error conditions. Adequate but could be more thorough.

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 descriptions fully cover each parameter, so description adds no extra meaning. Baseline 3 is appropriate since schema provides good parameter documentation; description does not compensate for 0% coverage in its own text.

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?

Uses specific verbs 'merge multiple raster datasets' and provides concrete examples (tiles, scenes, DEM sheets, image bands). Distinct from sibling tools like merge_features or clip_raster by focusing on raster mosaicking.

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?

Clearly states use case (combining tiles/scenes) and prerequisite (two or more input rasters). Lacks explicit when-not-to-use or alternative tool mentions, but context from sibling list suffices for differentiation.

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