Skip to main content
Glama
BnJam

STAC MCP Server

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
NameRequiredDescriptionDefault
idsNoList of specific item IDs to retrieve.
bboxNoBounding box [west, south, east, north] or GeoJSON geometry.
limitNoMaximum number of items to return.
queryNoQuery filter for properties.
fieldsNoList of fields to include/exclude (e.g., ["id", "properties.datetime"]). Prefix with "-" to exclude (e.g., ["-properties.eo:cloud_cover"]).
sortbyNoSort order (e.g., ["-properties.datetime"] for descending, ["+properties.datetime"] for ascending).
datetimeNoDatetime filter (e.g., "2020-01-01/2020-12-31").
intersectsNoGeoJSON geometry for spatial intersection query.
catalog_urlNoOptional catalog URL override.
collectionsNoOne or more collection IDs to search.
sign_assetsNoIf True and catalog is Planetary Computer, sign asset URLs for direct access. Requires planetary-computer package.
output_formatNoOutput format ("text" or "json").text

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
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.

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/BnJam/stac-mcp'

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