Skip to main content
Glama

get_sensor_registry_info

Retrieve details about available sensors in the STAC geospatial catalog to identify data sources for satellite imagery, weather, and other spatial datasets.

Instructions

Get information about the STAC sensor registry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler for 'get_sensor_registry_info', decorated with @app.tool for registration, proxies execution to the inner 'sensor_registry_info' tool.
    @app.tool
    async def get_sensor_registry_info() -> list[dict[str, Any]]:
        """Get information about the STAC sensor registry."""
        return await execution.execute_tool(
            "sensor_registry_info",
            arguments={},
            catalog_url=None,
            headers=None,
        )
  • Core handler function that executes the tool logic for sensor_registry_info, serializing the SensorDtypeRegistry contents into a dictionary.
    def handle_sensor_registry_info(
        _client: Any,
        _arguments: dict[str, Any],
    ) -> dict[str, Any]:
        """Handle the sensor_registry_info tool.
    
        Returns a mapping of collection ids to their sensor dtype info.
        """
        registry_info: dict[str, Any] = {}
        for collection_id, sensor_info in SensorDtypeRegistry.registry.items():
            registry_info[collection_id] = {
                "default_dtype": str(sensor_info.default_dtype),
                "band_overrides": {
                    k: str(v) for k, v in sensor_info.band_overrides.items()
                },
                "ignore_asset_name_substrings": sensor_info.ignore_asset_name_substrings,
            }
        return {"sensor_registry": registry_info}
  • Dispatch registry mapping tool names to handlers, including 'sensor_registry_info' to handle_sensor_registry_info.
    _TOOL_HANDLERS: dict[str, Handler] = {
        "search_collections": handle_search_collections,
        "get_collection": handle_get_collection,
        "search_items": handle_search_items,
        "get_item": handle_get_item,
        "estimate_data_size": handle_estimate_data_size,
        "get_root": handle_get_root,
        "get_conformance": handle_get_conformance,
        "get_queryables": handle_get_queryables,
        "get_aggregations": handle_get_aggregations,
        "sensor_registry_info": handle_sensor_registry_info,
    }
  • SensorDtypeRegistry class with static registry dictionary containing dtype information for various STAC collections/sensors, used by the handler.
    class SensorDtypeRegistry:
        """Registry that maps exact collection ids (lower-cased) to SensorInfo.
    
        Edit the `registry` dict to add explicit, exact collection id mappings.
        """
    
        registry: ClassVar[dict[str, SensorInfo]] = {
            # Sentinel / Copernicus
            "sentinel-2-l2a": _make_si("uint16", {"scl": "int8"}),
            "sentinel-2-l1c": _make_si("uint16"),
            # AWS Earth Search uses the 'collection 1' ids (sentinel-2-c1-l2a). The
            # Planetary Computer uses the simpler 'sentinel-2-l2a' id. Provide
            # catalog_aliases so callers can resolve catalog-specific ids.
            "sentinel-2-c1-l2a": _make_si(
                "uint16",
                {"scl": "int8"},
                None,
                {"https://earth-search.aws.element84.com/v1": "sentinel-2-c1-l2a"},
            ),
            "sentinel-2-pre-c1-l2a": _make_si(
                "uint16",
                {"scl": "int8"},
                None,
                {"https://earth-search.aws.element84.com/v1": "sentinel-2-pre-c1-l2a"},
            ),
            "sentinel-1-grd": _make_si("float32"),
            "sentinel-1-rtc": _make_si("float32"),
            "sentinel-3-olci-lfr-l2-netcdf": _make_si("float32"),
            "sentinel-5p-l2-netcdf": _make_si("float32"),
            # Landsat
            "landsat-c2-l2": _make_si("uint16", {"qa": "uint16"}),
            "landsat-c2-l1": _make_si("uint16", {"qa": "uint16"}),
            # HLS
            "hls2-s30": _make_si("uint16", {"scl": "int8"}),
            "hls2-l30": _make_si("uint16", {"scl": "int8"}),
            # MODIS
            "modis-09a1-061": _make_si("int16"),
            "modis-09q1-061": _make_si("int16"),
            # NAIP
            "naip": _make_si("uint8"),
            # Climate / gridded
            "daymet-daily-pr": _make_si("float32"),
            "daymet-daily-na": _make_si("float32"),
            "daymet-annual-na": _make_si("float32"),
            "daymet-monthly-na": _make_si("float32"),
            "gridmet": _make_si("float32"),
            "terraclimate": _make_si("float32"),
            "era5-pds": _make_si("float32"),
            # DEMs
            "cop-dem-glo-30": _make_si("float32"),
            "cop-dem-glo-90": _make_si("float32"),
            "3dep-seamless": _make_si("float32"),
            "3dep-lidar-dsm": _make_si("float32"),
            "3dep-lidar-dtm": _make_si("float32"),
            "3dep-lidar-intensity": _make_si("float32"),
            # Misc
            "gpm-imerg-hhr": _make_si("float32"),
            "nasadem": _make_si("float32"),
            "hgb": _make_si("float32"),
            "ms-buildings": _make_si("uint8"),
            "io-lulc": _make_si("uint8"),
            "us-census": _make_si("uint8"),
        }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying a read-only operation, but doesn't specify details like response format, error handling, authentication needs, or rate limits. For a tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized for a simple tool, with zero waste or redundancy.

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 0 parameters, an output schema exists, and no annotations, the description is minimally adequate. However, it lacks context about what 'information' includes or how it differs from sibling tools, which could help the agent use it correctly. The output schema may cover return values, but the description doesn't provide enough guidance for optimal tool selection.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, and baseline 4 applies as it doesn't detract from the schema's completeness.

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 verb ('Get') and resource ('information about the STAC sensor registry'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_collection' or 'get_root' that also retrieve information, leaving room for ambiguity about when this specific tool is appropriate versus others.

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 like 'get_collection' or 'get_root', nor does it mention any prerequisites or context for usage. It lacks explicit when/when-not statements or named alternatives, leaving the agent to infer usage based on tool names alone.

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

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