Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Power Rate Cases (rulings + ROE distribution by commission) [beta]

sec_power_rate_cases
Read-onlyIdempotent

Utility rate-case rulings panel + ROE-distribution-by-commission summary. Every row is one case: which utility, which commission (FERC / Texas PUC / state IOU commissions / etc.), ruling date, revenue increase, allowed ROE, effective date, outcome (approved / settled / denied / withdrawn / partial), summary text, source filing.

Returns a roe_distribution_by_commission summary: n_cases, mean / median / min / max allowed_ROE by commission_jurisdiction. The 'what ROE did the Texas PUC allow in recent cases' question answered in one call, plus the cross-commission comp set for utility-DCF work.

Filter by commission, outcome, filer (ticker_or_cik), or date range. Survivorship-complete back to 1994.

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_rate_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoruling_date ISO upper bound.
fromNoruling_date ISO lower bound.
as_ofNoPIT as-of — filed_at <= as_of applied BEFORE DISTINCT ON dedup.
limitNo
outcomeNoOutcome filter (approved / settled / denied / withdrawn / partial / etc.).
commissionNoCommission filter — FERC / 'Texas PUC' / 'Indiana Utility Regulatory Commission (IURC)' / etc. Substring ILIKE match.
ticker_or_cikNo

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 establish read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower. The description still adds real context: coverage is survivorship-complete back to 1994, rows are one-per-case with a defined field set, and the aggregate summary structure is disclosed. Pagination behavior and the LIMIT default of 100 are never explained, which is the main remaining gap.

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 identity of the tool, then the row shape, then the summary payload, then filters and coverage. Each block earns its place. Minor waste in promotional phrasing ('answered in one call') and in field lists that partly overlap the schema.

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?

With no output schema, the description carries the return-value burden and does so: it enumerates row fields and the roe_distribution_by_commission metrics (n_cases, mean/median/min/max allowed_ROE). For a 7-parameter, filter-heavy analytical tool the only real omissions are pagination/limit semantics and how dedup interacts with filters other than as_of.

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 coverage is 71%, so the schema already documents from/to, as_of, outcome and commission. The description adds the useful mapping that ticker_or_cik is a 'filer' identifier and that filters span commission, outcome, filer and date range. It says nothing about limit (undocumented in both places) or about substring matching behavior for commission beyond what the schema states, so it does not fully compensate.

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 pair: a utility rate-case rulings panel (one row per case, with enumerated fields) plus an ROE-distribution-by-commission summary. An agent knows exactly what it gets back. It does not explicitly contrast itself with sibling power tools (capacity events, demand forward, fundamentals), which keeps it just short of a 5.

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 description names concrete use contexts: "what ROE did the Texas PUC allow in recent cases" and "the cross-commission comp set for utility-DCF work." That is clear when-to-use guidance. It offers no when-not-to-use or explicit fallback to a sibling, so it falls short of the routing precision a 5 requires.

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