Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Power Fundamentals (per-ticker capacity/demand/outage panel + rate cases + coverage) [beta]

sec_power_fundamentals
Read-onlyIdempotent

Per-ticker power-sector fundamentals — a utility/IPP's year-by-year operating panel in one call: panel[] (capacity added/retired MW + net-by-fuel, firm data-center/large-load demand + YoY, outage count/MW, per year), identity (role / ISO / regulated-vs-merchant / is_active), rate_cases[] (commission rulings: allowed_roe, revenue increase, outcome), and coverage (a bool per dataset). Powers inferno's SIC-routed power section.

coverage is load-bearing, not decorative — a ticker can have real capacity + rate-case data but ZERO demand/outage extraction (AEP has no firm data-center commitments in the corpus). A naive zero would read as 'no data-center commitments' (false) vs 'none extracted' (the real state). Check coverage.demand before reading a 0 as a finding.

panel = last 10 years WITH DATA (not last 10 calendar years) — for a sparsely-covered ticker this can span decades (AEP's top-10 spans 1991-2025). Blank recent years are omitted rather than zero-filled.

Rate-case honesty: we surface allowed_roe (the OUTCOME ROE), revenue_increase_dollars, decided_date, status — NOT requested_roe, rate_base_usd, or the commission filed_date (not extracted; a v2 ask, not a silent null-map). allowed_roe hasn't had a two-model QA pass — rows outside a plausible utility band [3%, 20%] carry allowed_roe_suspect=true (rare mis-extraction, e.g. a rate adjustment read as the ROE).

Methodology: filer-disclosed SEC extractions only (not the full universe), per the sec_power_* family. Input: ticker_or_cik.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker_or_cik": "<ticker_or_cik>"
    },
    "name": "sec_power_fundamentals"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticker_or_cikYesUtility/IPP ticker (e.g. 'AEP', 'DTE') or CIK. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond them: coverage is a bool-per-dataset validity flag, panel is 'last 10 years WITH DATA' with blanks omitted rather than zero-filled, sparse tickers can span decades, and only filer-disclosed SEC extractions are covered rather than the full universe.

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 what the tool returns before any caveats, and nearly every sentence carries operative information (coverage semantics, panel window, missing rate-case fields, suspect ROE flag). It is dense and long, with some editorial phrasing ('load-bearing, not decorative', 'a v2 ask, not a silent null-map') that could be tightened without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the full return-value burden and does so precisely — naming each returned block and its fields. It also discloses the known extraction gaps (requested_roe, rate_base_usd, filed_date absent) and the allowed_roe_suspect QA caveat, so nothing an agent needs in order to interpret results correctly is missing.

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?

There is a single parameter at 100% schema coverage, and the schema already documents ticker-or-CIK format with examples. The description adds nothing about the parameter beyond restating 'Input: ticker_or_cik', so the schema carries this dimension entirely; baseline 3.

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 opening sentence names a specific verb-and-resource combination ('Per-ticker power-sector fundamentals ... operating panel in one call') and enumerates exactly what comes back (panel[], identity, rate_cases[], coverage). An agent can tell this is the aggregated per-ticker panel rather than a single-dataset sibling like sec_power_outages without opening any 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?

Usage context is clear — it is the one-call union of the sec_power_* datasets and it 'powers inferno's SIC-routed power section' — and it gives real guidance on reading the results (check coverage.demand before treating a 0 as a finding). It does not explicitly say when to route to the narrower siblings instead, so it stops short of full when/when-not routing.

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