Skip to main content
Glama

AI Buildout Permits

Pipeline Series

pipeline_series
Read-onlyIdempotent

Counts of data-center events or projects over time (by month, quarter or year), grouped by state, ticker, event type or source, dated by the record's own date or by first-seen date. Requires a subscription.

Example questions:

  • "Texas data-center certifications per quarter since 2023"

  • "Monthly moratorium and rezoning items by state this year"

  • "Certifications by tenant ticker per year"

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

Input Schema

NameRequiredDescriptionDefault
fromNoISO date to start from.
stateNoTwo-letter US state code, e.g. TX, VA, OH.
measureNo
group_byNo
intervalNo
date_basisNo
event_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile requires nothing more. The description's one genuine addition is the subscription requirement, which is an access precondition not visible in structured fields. It still says nothing about result size, limits, or what happens when the range is unbounded.

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 defining capability is front-loaded in the opening sentence, with the subscription caveat immediately attached, and the example questions are compact and illustrative rather than padding. The opening sentence is dense but carries no wasted wording.

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?

With 7 parameters and none required, defaults matter, yet the description never says what interval, date_basis, measure, or group_by default to, nor what happens when `from` is omitted. Since no output schema exists, the phrase 'counts ... over time' only roughly signals the return shape. Adequate for orientation, incomplete for correct invocation.

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?

Schema coverage is only 29%, so the description must compensate, and it does for most enum parameters: interval is glossed as month/quarter/year, group_by as state/ticker/event_type/source, date_basis as the record's own date versus first-seen, and measure as events versus projects. It leaves the event_type filter values and the `from` parameter unexplained beyond the schema.

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?

States a specific verb+resource: counts of data-center events or projects over time, with the grouping and date-basis dimensions spelled out. It is clearly an aggregation tool, distinguishable from detail-oriented siblings like project_detail or find_projects, though no sibling is named explicitly.

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 (Texas certifications per quarter, monthly moratorium/rezoning by state, certifications by ticker per year) give an agent strong, actionable usage context, and the subscription requirement is stated as a precondition. What's missing is any explicit exclusion or named alternative for row-level lookups.

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.