STAC MCP Server

Overview Schema Source Related Servers Discussions Admin

search_items

Search for geospatial items across STAC APIs using spatial, temporal, and property filters to retrieve satellite imagery and other assets.

Instructions

Search for STAC items.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	No	List of specific item IDs to retrieve.
`bbox`	No	Bounding box [west, south, east, north] or GeoJSON geometry.
`limit`	No	Maximum number of items to return.
`query`	No	Query filter for properties.
`fields`	No	List of fields to include/exclude (e.g., ["id", "properties.datetime"]). Prefix with "-" to exclude (e.g., ["-properties.eo:cloud_cover"]).
`sortby`	No	Sort order (e.g., ["-properties.datetime"] for descending, ["+properties.datetime"] for ascending).
`datetime`	No	Datetime filter (e.g., "2020-01-01/2020-12-31").
`intersects`	No	GeoJSON geometry for spatial intersection query.
`catalog_url`	No	Optional catalog URL override.
`collections`	No	One or more collection IDs to search.
`sign_assets`	No	If True and catalog is Planetary Computer, sign asset URLs for direct access. Requires planetary-computer package.
`output_format`	No	Output format ("text" or "json").	text

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv6.5.0Aug 8, 2026

changedInput schema / properties / collections / anyOf

Previous value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / collections / default
```
Added value: +null
```

addedInput schema / properties / ids

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "List of specific item IDs to retrieve."
+}

addedInput schema / properties / intersects

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "GeoJSON geometry for spatial intersection query."
+}

addedInput schema / properties / sortby

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Sort order (e.g., [\"-properties.datetime\"] for descending,\n    [\"+properties.datetime\"] for ascending)."
+}

removedInput schema / required
```
Removed value: -[
-  "collections"
-]
```

Changed10 schema fields changedv6.3.0Aug 7, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / bbox / description

Added value: +"Bounding box [west, south, east, north] or GeoJSON geometry."

addedInput schema / properties / catalog_url / description
```
Added value: +"Optional catalog URL override."
```
addedInput schema / properties / collections / description
```
Added value: +"One or more collection IDs to search."
```

addedInput schema / properties / datetime / description

Added value: +"Datetime filter (e.g., \"2020-01-01/2020-12-31\")."

addedInput schema / properties / fields

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "List of fields to include/exclude (e.g., [\"id\", \"properties.datetime\"]).\n    Prefix with \"-\" to exclude (e.g., [\"-properties.eo:cloud_cover\"])."
+}

addedInput schema / properties / limit / description

Added value: +"Maximum number of items to return."

addedInput schema / properties / output_format / description
```
Added value: +"Output format (\"text\" or \"json\")."
```
addedInput schema / properties / query / description
```
Added value: +"Query filter for properties."
```

addedInput schema / properties / sign_assets

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": false,
+  "description": "If True and catalog is Planetary Computer, sign asset URLs\n         for direct access. Requires planetary-computer package."
+}

Changed31 schema fields changedv1.0.0Jan 3, 2026

addedInput schema / properties / bbox / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "number"
+    },
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / bbox / default
```
Added value: +null
```

removedInput schema / properties / bbox / description

Removed value: -"Bounding box [west, south, east, north] in WGS84"

removedInput schema / properties / bbox / items
```
Removed value: -{
-  "type": "number"
-}
```
removedInput schema / properties / bbox / maxItems
```
Removed value: -4
```
removedInput schema / properties / bbox / minItems
```
Removed value: -4
```
removedInput schema / properties / bbox / type
```
Removed value: -"array"
```

addedInput schema / properties / catalog_url / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / catalog_url / default
```
Added value: +null
```

removedInput schema / properties / catalog_url / description

Removed value: -"STAC catalog URL (optional, defaults to Microsoft Planetary Computer)"

removedInput schema / properties / catalog_url / type
```
Removed value: -"string"
```

addedInput schema / properties / collections / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / collections / description

Removed value: -"List of collection IDs to search within"

removedInput schema / properties / collections / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / collections / type
```
Removed value: -"array"
```

addedInput schema / properties / datetime / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / datetime / default
```
Added value: +null
```

removedInput schema / properties / datetime / description

Removed value: -"Date/time filter (ISO 8601 format, e.g., '2023-01-01/2023-12-31')"

removedInput schema / properties / datetime / type
```
Removed value: -"string"
```

addedInput schema / properties / limit / anyOf

Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / limit / description

Removed value: -"Maximum number of items to return"

removedInput schema / properties / limit / maximum
```
Removed value: -100
```
removedInput schema / properties / limit / minimum
```
Removed value: -1
```
removedInput schema / properties / limit / type
```
Removed value: -"integer"
```

addedInput schema / properties / output_format

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": "text"
+}

addedInput schema / properties / query / anyOf

Added value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / query / default
```
Added value: +null
```

removedInput schema / properties / query / description

Removed value: -"Additional query parameters for filtering items"

removedInput schema / properties / query / type
```
Removed value: -"object"
```
addedInput schema / required
```
Added value: +[
+  "collections"
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

First observedSep 21, 2025

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the tool searches for items, without mentioning return format, pagination, authentication, or effects of parameters like catalog_url and sign_assets.

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

Conciseness3/5

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

The description is a single sentence with no wasted words, but for a tool with 12 parameters and rich filtering capabilities, it underuses the opportunity to summarize key features. It is concise but not informative enough.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema and complex parameters, but the description fails to address usage context, alternatives, or behavioral expectations. This is a minimal description for a complex search tool, leaving significant gaps in understanding.

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 description coverage is 100%, so the schema already fully documents all 12 parameters. The description adds no additional parameter semantics, but the baseline of 3 applies because the schema does the heavy lifting.

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 'Search for STAC items' uses a specific verb and resource, clearly indicating the tool's core function. However, it does not differentiate from sibling tools like search_collections or get_item, which also operate on STAC data.

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?

The description provides no guidance on when to use this tool versus alternatives. Sibling tools such as search_collections and get_item exist, but no comparative context or exclusions are mentioned.

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

Deploy Server