Skip to main content
Glama

Find power infrastructure

find_power_infrastructure

Locate nearby electricity grid elements: power lines, cables, substations, transformers. Filter by minimum voltage and power type, and retrieve distance-sorted results with optional geometry.

Instructions

Query the electricity grid layer around a location: power lines (high/low voltage), underground cables, substations and transformers — with voltage, circuits, operator and optional line geometry. Pass power_types to also include towers, poles, switches, converters, etc. Results are sorted by distance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of elements to return
radiusNoSearch radius in meters
latitudeYesCenter point latitude (decimal degrees)
longitudeYesCenter point longitude (decimal degrees)
min_voltageNoOnly return elements whose voltage tag is at least this value, in volts (e.g., 225000 for 225 kV). Elements without a voltage tag are excluded.
power_typesNoOSM power=* values to search for. Defaults to ["line","minor_line","cable","substation","transformer"]; other supported values include ["tower","pole","portal","switch","converter","compensator","insulator","terminal","catenary_mast"] (towers/poles are numerous — request them explicitly).
include_geometryNoInclude the full geometry of lines/cables (larger response)
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses sorting by distance, optional line geometry, and the ability to include more types. However, it omits behavior like default power_types, potential data incompleteness, or response size implications, making it adequate but not comprehensive.

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?

The description is two sentences, front-loaded with the core action and resource. Every sentence earns its place, covering purpose, key return elements, optional parameters, and sorting behavior without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 7 parameters and no output schema, the description adequately covers the return content (voltage, circuits, operator, geometry), sorting, and extension mechanisms. It could mention pagination or response limits, but the given detail provides a solid overview.

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%, so the baseline is 3. The description adds valuable context for power_types (listing examples like towers/poles) and include_geometry ('optional line geometry'), but it does not fundamentally enhance understanding beyond the schema's parameter descriptions.

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?

The description uses a specific verb 'Query' and names the resource 'electricity grid layer' with enumerated components (power lines, underground cables, substations, transformers). This clearly distinguishes it from sibling tools like find_power_plants or find_ev_charging_stations, which operate on different infrastructure.

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?

The description states the query context ('around a location') and provides guidance on extending results via power_types for additional element types. However, it does not explicitly name alternatives or when-not-to-use cases, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/visuelconcept/myosm-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server