Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Power Capacity Events (per-unit add/retire pipeline) [beta]

sec_power_capacity_events
Read-onlyIdempotent

Per-unit capacity add/retire pipeline from SEC disclosures. The row-level view that backs sec_power_supply_curve aggregation — useful when the question is about specific units ('what's NextEra's gas-build pipeline', 'every coal retirement announced in 2024') rather than aggregate trends.

Filter by filer (ticker_or_cik), event_type ('addition' / 'retirement'), fuel (coal / gas / gas_ccgt / gas_peaker / wind / solar / battery / nuclear / hydro / biomass / oil), status ('announced' / 'permitted' / 'under_construction' / 'completed' / 'cancelled'), ISO/RTO market, or target-year range.

Returns: filer_cik, unit_name_raw, event_type, fuel_type, mw, target_dt (COD), status, location_state, primary_iso, disclosed_capex_dollars, plus the source_accession + filed_at + snippet for citation. Deduped to the latest filing per (filer, unit, event_type).

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

Input Schema

NameRequiredDescriptionDefault
isoNoISO/RTO market scope (PJM / ERCOT / CAISO / MISO / NYISO / ISO-NE / SPP / non-RTO).
fuelNoFuel type filter (coal / gas / gas_ccgt / gas_peaker / wind / solar / battery / nuclear / hydro / biomass / oil).
as_ofNoPoint-in-time as-of date — applies DISTINCT ON dedup with filed_at <= as_of BEFORE the dedup.
limitNoMax events (default 100, max 500).
statusNoStatus filter (announced / permitted / under_construction / completed / cancelled).
year_toNoUpper bound on target_year (default 2040).
year_fromNoLower bound on target_year (default 2024).
event_typeNoaddition or retirement.
ticker_or_cikNoFilter to one filer (ticker / CIK / name substring). Use sec_power_gazetteer to resolve.

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/closed-world, so the safety profile is covered. The description adds real behavior beyond that: the dedup rule ('latest filing per (filer, unit, event_type)') and the citation provenance fields (source_accession, filed_at, snippet). It does not discuss row-volume limits or the as_of dedup interaction in prose, which the schema handles, so it falls just short of a 5.

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?

Front-loaded with the core identity and the sibling contrast in the first sentence, then filtering and returns. The inline enumeration of every fuel and status value duplicates the schema and is the one block that does not earn its space, but overall it is tight and well ordered.

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 9-parameter, no-output-schema read tool, the description covers the three things an agent needs: what the rows are, how to filter them, and exactly which fields come back including citation fields. Only the pagination/limit ceiling and as_of dedup behavior are left entirely to the schema, which is a minor residual gap.

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 baseline is 3. The description enumerates the filter dimensions and their allowed values (fuel, status, event_type, ISO, target-year range), but that largely restates what the schema already documents; it adds no syntax or edge-case meaning for limit or as_of.

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?

States a specific resource and granularity: 'per-unit capacity add/retire pipeline from SEC disclosures', and explicitly positions it as 'the row-level view that backs `sec_power_supply_curve` aggregation'. An agent can immediately tell it apart from the aggregate sibling without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use rule with examples of the question shape that selects this tool ('what's NextEra's gas-build pipeline', 'every coal retirement announced in 2024') versus aggregate trends, which routes to sec_power_supply_curve. It also names sec_power_gazetteer for resolving the filer argument, so the pre-call step is covered too.

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