Skip to main content
Glama
isaaccorley

Planetary Computer MCP Server

by isaaccorley

download_data_tool

Download satellite and raster data using natural language queries, with automatic geocoding, cloud filtering, and RGB visualization generation.

Instructions

Download satellite/raster data from Microsoft Planetary Computer.

Automatically detects collection from natural language queries, handles geocoding for place names, downloads and crops data, generates RGB visualizations.

Parameters

query : str Natural language query describing the data you want. Examples: "sentinel-2 imagery", "landsat", "naip aerial photos", "elevation data", "land cover" aoi : str or list[float] Required. Area of interest as either: - Place name string: "Seattle, WA", "Paris, France", "Central Park, NY" - Bounding box list: [west, south, east, north] in degrees Example: [-122.4, 47.5, -122.3, 47.6] time_range : str or None, optional ISO8601 datetime range. Defaults to last 7 days if not provided. Examples: "2024-01-01/2024-01-31", "2024-06-01/2024-06-30" output_dir : str, optional Directory to save outputs. Defaults to current directory. max_cloud_cover : int, optional Maximum cloud cover percentage for optical data (0-100). Default: 20

Returns

list[TextContent] File paths and metadata

Examples

Download recent Sentinel-2 imagery of Paris: query="sentinel-2 imagery", aoi="Paris, France"

Download Landsat for a specific bbox and time: query="landsat", aoi=[-122.4, 47.5, -122.3, 47.6], time_range="2024-06-01/2024-06-30"

Download NAIP aerial imagery: query="naip aerial photos", aoi="Central Park, NY"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
aoiYes
time_rangeNo
output_dirNo.
max_cloud_coverNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description discloses key behaviors: automatic collection detection, geocoding, cropping, and RGB visualization. It also mentions the output directory default. However, it omits important traits such as overwrite behavior, disk usage, network requirements, and error handling.

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?

The description is well-structured with sections for general description, parameters, returns, and examples. It is front-loaded with the core purpose. While detailed, it avoids repetition and unnecessary content; minor improvements could tighten the opening sentence.

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?

Given the tool has an output schema (mentioned in context) and 5 parameters, the description covers the main functionality but lacks operational context such as rate limits, data size restrictions, internet requirements, and error handling. More completeness would benefit an agent.

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

Parameters5/5

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

The input schema has no descriptions (0% coverage), so the description fully compensates. Each parameter is explained with types, defaults, and concrete examples (e.g., aoi accepts place names or bboxes, time_range format). This adds significant value beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool downloads satellite/raster data from Microsoft Planetary Computer and mentions automatic collection detection, geocoding, and visualization. However, it does not explicitly contrast with the sibling tool (download_geometries_tool), which would strengthen purpose clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus the sibling or alternatives. There is no mention of prerequisites, constraints, or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/isaaccorley/planetary-computer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server