Skip to main content
Glama

AI Buildout Permits

What's New

whats_new
Read-onlyIdempotent

Dated events on US data-center projects, newest first: Texas certifications, air-permit filings and listings, planned on-site generators, rezonings, moratoria, abatements and other city/county agenda items, and changes this ledger detected (status, tenant, delisting). Each event has its project, place, tenant or operator, tickers, the record link and a project page link. Returns the true total.

Example questions:

  • "What data centers got certified in Texas this month?"

  • "Which counties voted on data-center moratoria lately?"

  • "Any new data-center air permits in Virginia?"

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows per page with a subscription (max 200).
sinceNoISO date (YYYY-MM-DD). Default: 30 days ago.
stateNoTwo-letter US state code, e.g. TX, VA, OH.
offsetNo
event_typeNocertified, air_permit, rezoning, moratorium, abatement, land_use (any agenda item), generator, changes, withdrawn.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description only needs to add context, which it does: ordering is newest first, the response includes a true total, and each event carries project, place, tenant/operator, tickers and links. It does not mention rate limits or pagination behavior, but the core behavioral picture is solid.

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 core purpose and event taxonomy are front-loaded in the first sentence, followed by return fields and then example questions. It is efficient, though the event-type enumeration partly duplicates the enum and the example questions add length that could be trimmed without losing much.

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?

There is no output schema, so the description carries the return-value burden, and it does so by listing the fields present on each event plus the true total. Combined with the schema's default and limit details, an agent has enough to call this correctly, with only minor gaps around subscription-based paging behavior.

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 80%, so the baseline is 3. The description reinforces what the event_type values mean and implies state filtering through the examples, but it adds little syntax or semantics beyond what the schema already documents for since, limit, offset and state.

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 description states a specific resource: dated events on US data-center projects, newest first, with an enumerated list of event categories and return fields. It clearly distinguishes itself in substance from project lookup or search tools, but never names a sibling or states an explicit boundary, so it falls just short of the top score.

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?

Three concrete example questions directly show the kinds of queries this tool answers, which gives an agent clear context for when to reach for it. It doesn't state exclusions or name alternative tools for adjacent needs, so the guidance is clear but not exhaustive.

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.