Skip to main content
Glama

Sentinelhub Catalog Search

sentinelhub_catalog_search
Read-onlyIdempotent

Which satellite scenes are available for an area + time, searches the Sentinel-2 catalog (STAC) and returns matching scenes with acquisition datetime and cloud cover. Example: sentinelhub_catalog_search({ bbox: [12.44, 41.87, 12.53, 41.93], date_from: "2023-06-01", date_to: "2023-06-30", limit: 10, _apiKey: "client_id:client_secret" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bbox": [
        12.44,
        41.87,
        12.53,
        41.93
      ],
      "limit": 10,
      "_apiKey": "your-sentinel-hub-api-key",
      "date_to": "2023-06-30",
      "date_from": "2023-06-01"
    },
    "name": "sentinelhub_catalog_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
bboxYesBounding box [minLon, minLat, maxLon, maxLat] in EPSG:4326.
limitNoMax scenes to return (default 10, max 50).
_apiKeyYesSentinel Hub OAuth credentials as "client_id:client_secret" (from sentinel-hub.com or free at dataspace.copernicus.eu).
date_toYesEnd date, YYYY-MM-DD.
date_fromYesStart date, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive behavior, so the safety profile is covered. The description adds that the source is restricted to Sentinel-2 STAC and that results include datetime and cloud cover, but says nothing about pagination, rate limits, or empty-result behavior.

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 purpose and return fields are front-loaded in the first sentence, with the example in the second. The example largely duplicates the schema's own examples field, which is mild redundancy, but nothing is padded or confusing.

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?

With no output schema, the description correctly compensates by naming the returned fields (acquisition datetime, cloud cover). Annotations cover the safety profile and the schema covers all parameters, so an agent has what it needs to call the tool, though alternatives for non-Sentinel-2 data are not addressed.

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 coverage is 100%, so bbox, dates, limit and _apiKey are already documented with formats and defaults. The description's worked example restates those same parameters with realistic values but adds no semantics not already in the schema; baseline 3 applies.

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 names a specific verb and resource: searches the Sentinel-2 catalog (STAC) for scenes matching an area and time, returning acquisition datetime and cloud cover. The mentioned return fields (datetime, cloud cover) implicitly distinguish it from an analysis sibling like sentinelhub_ndvi_stats, but no sibling is named explicitly.

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

Usage Guidelines3/5

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

The phrasing 'Which satellite scenes are available for an area + time' implies the discovery use case, but there is no explicit when-to-use vs when-not guidance and no alternative tool is named. Usage must be inferred from the question framing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.