Skip to main content
Glama

search_dams

Read-onlyIdempotent

Search federally supervised Swiss dams and reservoirs by partial name to find SFOE dam records. Enter a name like Grimsel or Lac des Dix to locate matching dams.

Instructions

Search federally supervised dams by dam or reservoir name (SFOE)

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": {
      "query": "<query>"
    },
    "name": "search_dams"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPartial name, e.g. Grimsel, Lac des Dix

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / query / description
      Previous value: -"Dam or reservoir name to search (e.g. 'Grimsel', 'Grande Dixence', 'Mattmark', 'Lac des Dix'). Partial names are supported."New value: +"Partial name, e.g. Grimsel, Lac des Dix"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without description help. The description adds two genuinely new facts beyond the annotations: the dataset is limited to federally supervised dams (SFOE) and the match covers both dam and reservoir names. It says nothing about result volume, ordering, or what a hit contains.

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?

One short sentence with the scope qualifier and the match key front-loaded; nothing is redundant or padded. It is arguably too terse rather than bloated, but there is no wasted wording to penalize.

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 one-parameter search tool with rich annotations and full schema coverage, the essentials are present, and no output schema means return values need not be described. However, an agent still cannot tell how this differs from get_dams_by_canton or whether results are a list of dams with IDs suitable for passing to get_dam_details, which is the main missing piece.

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% and the single parameter already carries its own description with examples ('Partial name, e.g. Grimsel, Lac des Dix'). The description's only addition is that reservoir names as well as dam names are matchable, which is useful but marginal; matching behavior (substring vs prefix), case sensitivity, and minimum length remain unspecified in both places.

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 gives a specific verb and resource ('Search federally supervised dams') plus the matching key ('by dam or reservoir name'), so an agent knows exactly what is queried. It does not distinguish itself from the sibling tools get_dams_by_canton and get_dam_details, leaving the agent to infer the split between name search, canton listing, and detail lookup.

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?

Usage is only implied: the phrase 'by dam or reservoir name' signals that this tool is for when you already have a name, and the '(SFOE)' tag hints at the data source. There is no explicit statement of when to prefer get_dams_by_canton (browsing by region) or get_dam_details (fetching one record), and no exclusions or prerequisites.

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