Skip to main content
Glama

Dams near a point

get_dams_nearby
Read-only

Find federally supervised dams within a chosen radius of a WGS84 point, ordered nearest first with exact distances.

Instructions

Dams under federal supervision within radius_km of a WGS84 point, nearest first, with exact distances. Example: {lat: 46.08, lon: 7.40, radius_km: 15}.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "get_dams_nearby"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesWGS84 latitude
lonYesWGS84 longitude
limitNo
radius_kmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only say readOnlyHint and openWorldHint; the description adds real behavioral detail beyond them — the results are sorted nearest-first, each carries an exact distance, and only federally supervised dams are included. It still doesn't say whether limit truncates silently or what permission/coverage gaps exist in the open-world dataset.

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

Conciseness5/5

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

Two short sentences: the capability statement is front-loaded and the concrete example earns its space by fixing coordinate format and radius scale. No filler.

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 must carry the return contract; it covers ordering and distance but not the shape of each dam record or how limit affects results. For a 4-parameter open-world geo query it is adequate but leaves notable 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 50%: lat/lon are documented in the schema and radius_km gets meaning from the description plus the example value. The limit parameter (default 10, max 50) is undocumented in both places, and the description neither confirms nor adds to the lat/lon bounds.

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 resource (dams under federal supervision) plus spatial scope (within radius_km of a WGS84 point) and result ordering. An agent can distinguish it from a name/text-based search such as search_dams, though the description never names that sibling explicitly.

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 implied by the phrasing (proximity search around a coordinate) and reinforced by the example invocation, but there is no explicit statement of when to prefer this over search_dams or the other nearby-* tools, nor any exclusions.

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