Skip to main content
Glama

WritersLogic verifiable AI agents

infrastructure-pipeline-brief

Grid, Tower & Infrastructure Pipeline Near a Site — Screens a US site (latitude/longitude or Census-geocoded address) within a radius (default 10, max 50 miles) using primary public data: operating and planned generators and storage from EIA Form 860M, active interconnection-queue entries from MISO, CAISO, NYISO and ERCOT matched at county level, FCC Antenna Structure Registration towers, and HIFLD transmission lines and substations. Code computes

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "infrastructure-pipeline-brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusNoWhich screening signals to emphasise. Default general.
addressNoUS street address, geocoded with the Census Bureau geocoder. Used when latitude/longitude are absent.
latitudeNoWGS84 latitude of the site (United States and territories). Give latitude and longitude together, or address.
longitudeNoWGS84 longitude of the site.
radius_milesNoSearch radius in miles (default 10, clamped to at most 50).
window_yearsNoWindow for capacity added within the radius (default 3 years).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden. It does useful work by naming the upstream data sources and their vintage (EIA 860M, HIFLD), and by stating radius clamping behavior, but the truncated final sentence removes any statement of what is computed, returned, or how fresh/large the result is.

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

Conciseness2/5

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

It is one very long run-on sentence that terminates abruptly mid-thought ('Code computes '), which reads as a truncated definition rather than deliberate brevity. The front-loading is good, but an incomplete trailing clause is wasted and confusing text.

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?

Given six parameters, no output schema, and no annotations, the definition should explain what the screen produces and how results are shaped; the truncation leaves that entirely absent. The data-source inventory partially compensates, but an agent still cannot anticipate the response.

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 six parameters are already documented, and the description adds little per-parameter meaning beyond tying the screen to US sites. The 'focus' enum's five modes (data_center, logistics, telecom, solar_storage, general) are not elaborated anywhere in the prose, which is the one place added semantics would have paid off.

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?

The opening states a specific verb and resource ('Screens a US site ... within a radius') and enumerates the exact datasets consulted (EIA 860M, MISO/CAISO/NYISO/ERCOT queues, FCC ASR towers, HIFLD lines). An agent can tell this is a geospatial infrastructure-proximity screening tool, though the definition ends mid-clause ('Code computes ') so the description of the actual deliverable is missing.

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 framing ('Near a Site', 'US site') and the address-vs-latitude/longitude alternative is stated inline. However, there is no explicit guidance on when to prefer this over e.g. regional-economy-brief or dev-pipeline-toolkit, and no exclusions or prerequisites beyond the US-only scope.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources