Skip to main content
Glama

Swiss monitored glaciers (GLAMOS)

list_glaciers
Read-only

Search Swiss glaciers by name to retrieve SGI IDs, area, coordinates, and available measurement series such as length change, mass balance, and volume change.

Instructions

Glaciers in the Swiss monitoring network with SGI id, area (km²), coordinates and which measurement series exist (length change, mass balance, volume change). Filter by name; sorted by area. Example: {query: 'Aletsch'}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_glaciers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoName fragment, e.g. 'Rhone', 'Aletsch', 'Morteratsch'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.6/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 adds the content of each record and the default sort order by area, which is real behavioral context. It does not disclose result-set size behavior or how the limit parameter truncates results, leaving one 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 resource, followed by returned fields, filtering, sort order, and one compact example. The parenthetical series list is informative rather than filler, though the single long sentence could be split for easier scanning.

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?

With no output schema, the description usefully enumerates the returned fields, which is the right compensation. However, it omits any explanation of the limit parameter or what happens when more than 30 glaciers match, leaving an agent unsure about result completeness for a nationwide list.

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 50%: the query parameter is documented in the schema and reinforced by the description's 'Filter by name' plus an example fragment. The limit parameter (default 30, max 200) is documented only in the schema and gets no mention of pagination or truncation behavior in the description, so the description neither compensates nor adds much.

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?

Names a specific resource (glaciers in the Swiss monitoring network) and enumerates the returned fields (SGI id, area, coordinates, available measurement series), so it is distinguishable from sibling list tools like list_snow_stations or list_hydro_stations. It never uses an explicit verb such as 'list' or 'search', relying on the reader to infer the list semantics from the field enumeration.

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?

Implies usage through 'Filter by name; sorted by area' and a concrete call example {query: 'Aletsch'}, which tells an agent how to use the query parameter. There is no explicit when-to-use or when-not guidance and no named alternative among the many other list_* tools, so selection guidance stays implicit.

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