Skip to main content
Glama

Search and rank Swiss dams

search_dams
Read-only

Search Switzerland’s federal dam register by dam, reservoir, facility, purpose or type, then rank results by height, volume, crest length or year built.

Instructions

Search the federal dam register (SFOE, ~225 dams) by dam, reservoir or facility name, purpose (hydroelectricity, flood protection, irrigation, …) or dam type (arch, gravity, embankment, …), ranked by height, volume, crest length or year built. With no filters it ranks all dams, e.g. the tallest or largest. Examples: {query:'Dixence'}, {sort_by:'volume'}, {purpose:'flood'}.

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": "search_dams"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoe.g. arch, gravity, embankment, buttress
limitNo
orderNodesc
queryNoDam, reservoir or facility name (partial, accents optional)
purposeNoe.g. hydroelectricity, flood protection, irrigation, drinking water
sort_byNoheight

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real behavioral context beyond them: the data source (SFOE), the small corpus size (~225 dams, implying no deep paging), and the descending ranking behavior when no filters are given. It does not describe the fields returned per dam, which is the main remaining 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 and scope, then the facet list, then the no-filter rule and examples; nothing is padded. The opening sentence is overloaded with three parallel facet clauses and could be split, and the examples partly duplicate the schema enums.

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?

For a 6-parameter, zero-required read tool with no output schema and thin annotations, the definition covers what can be filtered and how results are ordered, which is the essential part. It leaves unclear what a result record contains and whether purpose/type matching is partial, so it is adequate rather than complete.

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?

With 50% schema coverage, limit and order are undocumented in both places, but their enums/defaults make them self-evident. The description restates the sort_by keys, type and purpose values that the schema already lists, and adds only the useful notion that filtering is optional and ranking applies globally — marginal value beyond the schema.

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 (search the federal dam register, SFOE, ~225 dams) and enumerates the searchable facets and ranking keys, so an agent can distinguish it from the spatial sibling get_dams_nearby without opening the schema.

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?

Explains the zero-filter case explicitly ("with no filters it ranks all dams, e.g. the tallest or largest") and supplies three concrete invocation examples, which gives clear context for when this tool fits. It stops short of naming the alternative or stating when-not to use it, so no explicit exclusion.

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