Skip to main content
Glama

get_dam_details

Read-onlyIdempotent

Retrieve full technical details for a named Swiss dam to support infrastructure research and analysis.

Instructions

Full technical details of one dam by name

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

Input Schema

NameRequiredDescriptionDefault
nameYese.g. Grande Dixence (see search_dams)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / name / description
      Previous value: -"Dam name (e.g. 'Grande Dixence', 'Spitallamm', 'Mattmark', 'Verzasca'). Use search_dams first if you are unsure of the exact name."New value: +"e.g. Grande Dixence (see search_dams)"
  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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds only that the response is "full technical details," without saying what fields are included, whether missing names error or return empty, or whether the lookup is exact-match or fuzzy.

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, front-loaded sentence with no filler. It is arguably over-terse for a lookup tool, but every word is load-bearing and nothing is wasted.

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 single-parameter detail lookup with no output schema, the essential purpose is conveyed, but the description never characterizes what "full technical details" covers (height, capacity, type, location) nor the failure behavior for unknown names. Adequate, with clear gaps.

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 an example ("Grande Dixence") plus a pointer to search_dams, so the baseline is 3. The description's phrase "by name" adds no format, casing, or exactness rules beyond what the schema already states.

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?

States a specific verb-resource pair: retrieve full technical details of a single dam, looked up by name. This is clearly distinguishable from search_dams and get_dams_by_canton, though the description does not name those siblings explicitly to reinforce 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 Guidelines3/5

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

"By name" implies the tool needs an exact name rather than filters, and the routing hint toward search_dams lives only in the parameter schema, not the description. No explicit when-to-use versus search_dams or get_dams_by_canton guidance is given in the description itself.

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