Skip to main content
Glama

List items and downloadable assets of a STAC collection

get_geodata_collection_items
Read-only

List items (tiles, stations, time slices) and assets of a data.geo.admin.ch STAC collection; filter by bbox, datetime, item ID or asset key to locate downloadable Swiss geodata files and metadata.

Instructions

List the items (tiles, stations, time slices) of a data.geo.admin.ch STAC collection with their downloadable assets (href, media type, size), plus collection-level assets (e.g. MeteoSwiss station/parameter metadata CSVs). Filter by WGS84 bbox, datetime or a single item id; asset_filter narrows asset keys. Examples: collection='ch.meteoschweiz.ogd-smn', item_id='ber' (Bern-Zollikofen station), asset_filter='d' (daily data); collection='ch.swisstopo.swissalti3d', bbox=[7.43,46.94,7.46,46.96]. Next: read_geodata_asset on a CSV/JSON href.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collection": "<collection>"
    },
    "name": "get_geodata_collection_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
bboxNoWGS84 bbox [minLon, minLat, maxLon, maxLat], e.g. [7.43, 46.94, 7.46, 46.96]
limitNoItems per page (default 10)
item_idNoFetch one item by id (e.g. a MeteoSwiss station abbreviation in lower case, 'ber')
datetimeNoRFC 3339 instant or interval, e.g. '2023-01-01T00:00:00Z/2023-12-31T23:59:59Z' or '2024-01-01T00:00:00Z/..'
page_urlNoThe 'next_page_url' from a previous call, to continue paging
collectionYesSTAC collection id
asset_filterNoOnly assets whose key/title contains this text, e.g. '.csv', '_h_recent', '2m'
include_collection_assetsNoAlso list collection-level assets (metadata files)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description still adds real behavioral context by naming the returned fields (href, media type, size), noting collection-level metadata assets are included by default, and indicating that asset_filter narrows keys rather than filtering items. It does not explain paging mechanics beyond the page_url parameter, which is the main residual gap.

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?

Front-loaded with the core purpose, then filters, then examples, then the next-step pointer — no filler sentences. It is dense and example-heavy in one block, which slightly hurts scannability, but every clause carries information.

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?

For an 8-parameter read tool with no output schema, the description adequately conveys what is returned, how filtering works, and where to go next. Remaining gaps — pagination loop behavior and the 1-100 limit bound — are minor since the schema documents limit and page_url directly.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by showing how parameters combine meaningfully (collection + item_id='ber', collection + bbox, asset_filter='_d_') and clarifying that asset_filter matches asset keys and collects collection-level metadata CSVs. The include_collection_assets and limit/page_url behaviors are only lightly touched, keeping it just short of a 5.

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

Purpose5/5

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

States a specific verb and resource ('List the items... of a data.geo.admin.ch STAC collection') and enumerates what comes back (downloadable assets with href, media type, size, plus collection-level assets). It is clearly distinguishable from siblings like search_geodata_collections (find collections) and read_geodata_asset (fetch a single file), and the closing 'Next: read_geodata_asset' reinforces the boundary.

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

Usage Guidelines4/5

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

Gives concrete when-to-use context through worked examples (filter by station id, bbox on swissalti3d, asset_filter='_d_') and an explicit handoff to read_geodata_asset for reading a returned href. It lacks an explicit 'do not use this to discover collections — use search_geodata_collections' exclusion, but the intent is inferable from the examples.

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

Deploy Server

Other Tools