GovBot Energy Infrastructure

View saved version →

---
name: generator-mix-brief
description: Prepare a dated EIA generator-capacity inventory brief for a state or balancing-authority code, preserving capacity measures, generator counts, storage units, source codes and missingness without implying generation or spare capacity.
---

Use this workflow for questions about a state or balancing authority's reported generator inventory or capacity mix. This independent service reads held public EIA datasets; it does not query a live grid or a real-time generator status service. Start with `describe_energy_layers` when the source period, available measures or coverage is not already in the conversation. The held preliminary monthly generator snapshot is August 2026; it is not the latest available month. Other held map layers have separate vintages. Quote the response's actual source metadata if a later authorized snapshot replaces it.

Use `summarize_generating_capacity` with the requested state, balancing-authority code, or both. A state may be a two-letter abbreviation or a supported two-digit FIPS code. Only apply a balancing-authority code if the person supplies or chooses a code present in the source; do not infer a territory from a location or invent a balancing-authority full name. If scope is missing, ask for a state or source balancing-authority code rather than a home address or precise personal location. Use the tool's real schema; do not invent date, generator-status or live-generation parameters.

Report what the summary actually measures. Nameplate capacity and net summer capacity are distinct MW measures; never silently substitute one for the other. Storage energy in MWh is a separate reported quantity, not power capacity and not generation. Do not calculate storage duration or annual generation from these inventories. Keep source energy-source, technology, prime-mover and balancing-authority labels/codes as supplied; an unavailable description stays unavailable. Do not treat a name, code or catalog status as evidence of current operation, ownership changes or environmental compliance.

Separate generator records, unique plants and entities. Use the returned whole-scope group totals, denominators and unknown-field counts; a list of examples is not the entire inventory. State the capacity measure and its coverage before comparing groups. Zero is a reported value; null or missing is unknown. Do not turn a group with missing capacity into a zero-capacity group. If a sum includes only known values, describe it as partial with its known/missing denominator. Do not derive new percentages unless requested and justified by a consistent complete denominator; if computed, label the arithmetic and scope explicitly. Avoid double-counting storage or overlapping technology/energy-source groups. Plant counts overlap across source groups and must not be added. The held operable inventory includes operating, standby and out-of-service statuses; preserve returned status codes/descriptions rather than calling every generator currently operating. `value`, `unit`, `known_count`, `missing_count` and `is_partial` describe each numerical subtotal; use those denominators for the measure itself. Storage denominators refer to the eligible storage rows, not all generators.

A useful brief leads with the selected state and dated capacity mix, then a compact table of returned measures and record counts, followed by missingness and source limits. Cite the EIA source URL, held data period, original source download date and held-read time separately. A new held-read time does not make the dataset current. Include Operating and separately supplied Operating_PR sheet scope only as actually relevant to the returned state. A missing state or no-match result is not proof of no physical infrastructure.

Refuse claims about actual generation in MWh, emissions, dispatch, available/spare/interconnection capacity, project feasibility or investment suitability when these are not supplied by the source. Explain that generator-capacity inventories cannot certify a connection or investment. No personal address lookup, property/safety/engineering/insurance certification or financial recommendation. A source/schema/asset failure means unavailable evidence, not an empty inventory. Offer a narrower supported historical inventory question rather than fabricated results.

View saved version →

---
name: nearby-energy-records
description: Prepare a source-qualified brief of held EIA plant/fuel-facility and DOE NETL/HIFLD transmission-line records near a public research point, distinguishing mapped facilities, generator inventory, source dates and approximate distances from actual availability or site suitability.
---

Use this workflow to research power-plant and fuel-facility records around a user-supplied public research point. Never request a home address, infer a device location, geocode a personal address or solicit a precise personal location. If coordinates are missing, ask for a public city-center reference point or another nonpersonal research scope. State supplied latitude, longitude and radius without expanding them silently.

Read `describe_energy_layers` to establish which held EIA datasets and facility types are actually available, their separate source periods and geometry/field limits. Transmission records come from the separate DOE NETL-hosted HIFLD layer, not EIA. Do not describe unsupported substations, service territories or environmental-enforcement records. These are energy inventory sources, not EPA enforcement records. The preliminary August 2026 generator workbook and map-layer vintages are distinct; never label every layer August 2026 or current.

Use `find_power_plants_near_point` for plant records and `find_fuel_facilities_near_point` for the supported fuel types requested. Preserve the schema's radius and limit bounds; validate latitude/longitude and reject invalid inputs before calling when apparent. Do not silently clip an invalid radius. Choose optional energy-source/facility-type values only from the actual schema/source catalog, preserving published codes rather than guessing labels. State which layers were searched. Do not call every layer or enlarge the radius merely to manufacture matches.

Lead with the queried scope and matching-record count, then the displayed examples. Preserve plant/facility identifiers and source-specific names/operator fields exactly; generator counts are not plant counts. Explain when capacity measures originate from generator inventory versus a mapped plant record. Nameplate MW, net summer MW and storage energy MWh must remain separate with missing values intact. Fuel-facility values retain their own source units: storage volumes, daily throughput/processing and annual production quantities are different measures and must not be added together. Report a historical throughput value only when supplied, with its unit and period. Do not infer generation, throughput, emissions, current operating status, ownership or available capacity from the location or name. Plant coordinate exclusion counts apply to the inventory, not just the query circle; disclose missing/conflicting-coordinate exclusions without inventing their locations.

Distances are references to held mapped locations, not surveyed setbacks or authoritative nearest physical features. Respect the returned ordering even where rounded distances tie. Separate returned rows from total matching records and any caps; a bounded search or incomplete layer is not a complete physical inventory. A facility in one source and a nearby corridor in another are not an established connection. Do not combine sources by name or proximity into an unsupported asset identity.

Cite each dataset's source URL and vintage, original download date and current held-read time separately. Explain differing periods across sources. Missing descriptions/coordinates/values remain unknown; a successful no-match applies only to that selected held scope. An error, missing asset or unavailable field is not zero infrastructure and does not establish safety or suitability.

End with the answer's practical boundary: these records support public infrastructure research, not a property decision, environmental clearance, service availability, interconnection study, financial recommendation or engineering/safety/insurance certification. For authoritative capacity or site decisions, direct the person to the relevant operator or qualified authority without promising acceptance. Keep the response useful with the supported inventory rather than merely listing disclaimers.

When electric transmission lines are requested, use `find_transmission_lines_in_area` with the supplied public point/radius or valid noncrossing research box. Do not automatically fetch them for unrelated plant/fuel questions. State the full matched hosted-record count, display limit and returned examples separately. Preserve reported owner/status, voltage kV, voltage class, inferred-voltage flag and unknown values. Negative numeric sentinels are unknown, not zero kV. kV is electrical voltage, not generation/transfer MW, spare capacity or connection availability. NETL credits HIFLD2022, retrieved2023; service edit date and GovBot download/read dates are distinct. Query geometry is generalized at offset0.0005degrees with5decimal serialization; neither establishes source accuracy. Do not join a nearby line to a plant as a connected system or infer who supplies a property. Retain source-specific credits, including OpenStreetMap contributor attribution when supplied. Historical/live outages and restoration estimates are excluded.

View saved version →

---
name: pipeline-corridor-records
description: Summarize held EIA pipeline and, when requested, DOE NETL/HIFLD transmission-line records intersecting a public research area, preserving source vintages, mapped geometry limits and counts without inferring exact routes, operating conditions or excavation safety.
---

Use this workflow for public research about EIA-mapped pipeline corridors. Start with `describe_energy_layers` to identify available pipeline types, source vintages, source URLs and geometry coverage. These held map layers are not current operator field drawings and do not inherit the August 2026 generator-workbook period. Electric transmission has its own DOE NETL/HIFLD source and operation; substations and utility service territories remain unsupported.

Accept a public research point and radius or an explicit bounding box. Use `find_pipelines_in_area` with exactly one of the supported geometry forms and any requested supported pipeline-type filter. Validate coordinate ranges, west/east and south/north ordering and size bounds against the actual schema. The service does not support an antimeridian-crossing box; do not silently reinterpret one. Ask for a smaller valid public area when a query is outside bounds. No home-address solicitation, device geolocation or property geocoding.

Report the held layers searched and the requested area before results. Separate `pipeline_groups_matching` from `returned` displayed groups and their limit. The service groups matching records by type and source attributes; per-group `matching_mapped_records` and layer counts count matched records, not unique physical systems. Do not label a group count as a segment or physical-pipeline count. A line record is not necessarily a unique named pipeline system, segment in operation or number of physical pipes. Preserve source identifiers and names; missing ownership/status/diameter/throughput/depth fields remain unknown and should not be inferred from the name, commodity or proximity. Do not join different layers into a single physical asset without source identity evidence.

Describe geometry as generalized EIA mapping. An area intersection or approximate mapped distance does not locate a pipe precisely on the ground, determine which side of a parcel it lies on, establish a connection, show a safe setback, or supply an excavation/tapping location. Keep any output distance units and approximation qualifiers together. Point searches use a local equirectangular closest-point approximation on mapped straight segments, with approximate radius-edge inclusion; a bounding-box query has no point-distance measure. Current held pipeline layers are January 2020 and omit local distribution and most gathering lines. Do not present a derived line length as an engineering length, authoritative route or guaranteed closest physical pipe. Preserve returned order when rounded distances tie.

Provide a short table only for requested fields that exist, then explain each layer's source vintage/coverage, original download date and held-read time. Source periods can differ across pipeline types and facilities. A fresh query/read timestamp is not evidence the corridor is current. Cite EIA's published source link for the specific layer when returned. Do not claim every constituent dataset shares a single public-domain license; retain source-specific attribution and terms.

No matches means no mapped records in the queried held scope, not absence of pipelines or permission to dig. Source/asset/schema errors are unavailable evidence, not empty results. Decline exact field route, depth, pressure, capacity availability, connection feasibility, operating condition, digging/tapping, safety, legal/insurance or financial determinations. Refer authoritative location and operational questions to the relevant operator or qualified authority; do not promise a result. Offer the supported historical corridor inventory with clearly bounded conclusions.

For an explicit pipeline/transmission comparison, call `find_transmission_lines_in_area` separately with the same valid public area and requested limit. Keep EIA pipeline groups and NETL-hosted HIFLD transmission records in separate result sections; their counts, source periods and identifiers are not interchangeable. Transmission credits are HIFLD2022, retrieved by NETL2023. Retain each returned owner/status/voltage/inferred flag and record source/date; unknown stays unknown. Voltage kV is not power MW, spare capacity or connectivity. Explain the returned query generalization settings and approximate distances; no engineering route precision. Cite NETL and supplied constituent credits. Historical/live outages and restoration estimates are excluded. No proximity-based plant/line identity or physical connection inference.