Skip to main content
Glama

AI Buildout Permits

Find Projects

find_projects
Read-onlyIdempotent

Searches US data-center projects in the public record by state, county, city, tenant (Texas occupant), operator or permittee, any named party, ticker, status, on-site gas generation, source or name. Each row gives status, tenant, operator, resolved tickers, private parents, stated on-site MW, the record link and a page link, plus the true total of matches.

Example questions:

  • "Which Texas data centers list Amazon as the tenant?"

  • "Planned data centers in Loudoun County with air permits"

  • "Data-center campuses with on-site gas turbines"

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": "find_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
limitNo
partyNoAny named party in any role.
queryNoWords in the project name.
stateNoTwo-letter US state code, e.g. TX, VA, OH.
countyNo
offsetNo
sourceNo
statusNo
tenantNoOccupant named on a certification (Texas), e.g. 'Anthropic', 'Amazon'.
tickerNoA resolved ticker, e.g. AMZN, ORCL, CRWV.
operatorNoOperator, owner or permittee name, e.g. 'Microsoft', 'Vantage'.
onsite_gasNoTrue: only projects whose records show on-site generation.
include_jurisdictionsNoAlso return city/county agenda records (Legistar).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond them by stating the shape of each returned row (status, tenant, operator, resolved tickers, private parents, stated on-site MW, record and page links) and that a 'true total of matches' is returned even under pagination. It says nothing about defaults, empty-filter behavior, or data freshness.

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?

The searchable-facet inventory is front-loaded in the first sentence, and the example questions are compact and each illustrate a distinct filter combination. The opening sentence is long and dense, but every clause names a real filter; nothing is filler.

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 14-parameter search tool with no output schema, the description usefully describes the returned row fields and the match total, which is exactly what would otherwise be missing. The remaining gaps — pagination defaults, maximum page size behavior, and what an unfiltered call returns — are real but minor for a read-only search.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 14 parameters at 57% schema coverage, the description compensates well for the undocumented ones: it clarifies that tenant is the Texas certification occupant, operator covers owner/permittee, and party is any named role — distinctions the schema does not make. It leaves limit/offset pagination behavior and the source enum values unexplained, so it does not fully close the coverage gap.

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 opens with a specific verb ('Searches') and a precisely scoped resource ('US data-center projects in the public record'), then enumerates the filter dimensions (state, county, city, tenant, operator, ticker, status, on-site gas, source). The three example questions make the domain boundary concrete, so an agent can tell this apart from a detail/record-lookup tool without opening the schema.

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 example questions give clear situational guidance ('Which Texas data centers list Amazon as the tenant?', 'Planned data centers in Loudoun County with air permits'), which maps each question to the relevant filter. There is no explicit when-not-to-use guidance or named alternative for follow-up detail lookups, so it stops 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.