Skip to main content
Glama

Ferc1 Income Statement

ferc1_income_statement
Read-onlyIdempotent

FERC Form 1 income statement (Schedule 114) for one utility and report year: operating revenues, operating expenses, taxes, net utility operating income, net income, in US dollars as filed, by line item and segment. The headline block gives total operating revenues and net income. Source: FERC Form 1 as processed by Catalyst Cooperative PUDL.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": 2023,
      "utility": "PacifiCorp"
    },
    "name": "ferc1_income_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoReport year (e.g. 2023). Default: the latest year on file for the respondent.
utilityYesFERC Form 1 respondent: a name (e.g. "PacifiCorp") or the numeric FERC respondent id (utility_id_ferc1, e.g. 303). Find ids with ferc1_find_utility.
utility_typeNoOptional filter on the business segment the rows describe: total, electric, gas, other. Default: all segments the respondent reported.

Output Schema

NameRequiredDescriptionDefault
foundNo
sourceNo
utilityNo
currencyNo
headlineNo
data_as_ofNo
line_itemsNo
attributionNo
report_yearNo
line_item_countNo
years_availableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's job is to add context — which it does: it discloses the data source (FERC Form 1 processed by Catalyst Cooperative PUDL), that values are in US dollars as filed, and that rows are broken out by line item and segment. The one gap is no note on how missing or unreported years are handled, but overall it adds meaningful context beyond the annotations.

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?

Three sentences, front-loaded with the resource and scope, then the return contents, then provenance. Minor redundancy in restating 'FERC Form 1' twice, but every sentence carries information and nothing is padding.

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?

An output schema exists, so return formatting need not be explained, and annotations carry the safety profile. The description is complete enough to call the tool correctly for a simple three-parameter lookup; the main omission is sibling routing (ferc1_income_history) for multi-year needs.

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 schema already documents year defaults, utility name-or-id forms, and the utility_type segment values. The description only loosely reinforces this by mentioning 'one utility and report year' and 'by line item and segment,' without adding format or edge-case detail 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?

The description names a specific resource (FERC Form 1 income statement, Schedule 114) and its scope (one utility, one report year) with the exact line-item categories returned. It is clear what the tool retrieves, though it never explicitly distinguishes itself from the sibling ferc1_income_history, leaving the agent to infer the single-year vs. multi-year split.

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

Usage Guidelines3/5

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

Usage context is implied by 'for one utility and report year,' and the description usefully routes the agent to ferc1_find_utility for obtaining ids. However, there is no explicit when-to-use/when-not guidance and no mention of ferc1_income_history as the alternative for multi-year pulls.

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.