Skip to main content
Glama

get_dams_by_canton

Read-onlyIdempotent

Retrieve federally supervised dams for a Swiss canton using its canton code and an optional result limit to find dam records for a specific region.

Instructions

Federally supervised dams in a canton

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": {
      "canton": "<canton>"
    },
    "name": "get_dams_by_canton"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDams to return (1-100)
cantonYesCanton code, e.g. VS

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • changedInput schema / properties / canton / description
      Previous value: -"Swiss canton 2-letter abbreviation code (e.g. 'VS' for Valais, 'GR' for Graubünden, 'BE' for Bern, 'UR' for Uri, 'TI' for Ticino, 'VD' for Vaud)."New value: +"Canton code, e.g. VS"
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 20,
      +  "description": "Dams to return (1-100)",
      +  "type": "number"
      +}
  2. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile needs no restating. The description adds one piece of context beyond that – the dataset is limited to 'federally supervised' dams, which signals a coverage filter an agent should know about – but says nothing about result ordering, truncation at the default limit, or empty-result behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At six words there is no padding, but it is a noun fragment rather than a sentence and omits the action verb. The brevity here reflects under-specification rather than disciplined editing.

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?

This is a simple two-parameter lookup with full schema coverage and a complete annotation set, and there is no output schema to explain, so the bar is low. Even so, the description leaves out routing guidance versus the three dam-related siblings, which is the main thing an agent needs and cannot get from structured fields.

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 description coverage is 100%: 'canton' is documented with an example ('VS') and 'limit' with its range (1-100) and default. The description adds no additional meaning about accepted canton codes, case sensitivity, or what limit truncation means, so the baseline 3 applies.

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

Purpose3/5

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

The phrase identifies the resource (federally supervised dams) and the scope (a canton), so an agent can infer it is a canton-filtered list. But there is no verb and the wording essentially restates the tool name, and it never distinguishes itself from the closely related siblings search_dams and get_dam_details.

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?

No when-to-use guidance is given: nothing says to prefer search_dams for keyword lookups or get_dam_details for a single record. The only implied usage cue is the 'canton' scope, which is already visible in the parameter name.

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