Skip to main content
Glama

Ferc1 Income History

ferc1_income_history
Read-onlyIdempotent

One FERC Form 1 income-statement line (default operating_revenues) for one utility across every report year on file, 1994 to date, for trends. Use ferc1_income_statement to see the available income_type names.

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": {
      "utility": "PacifiCorp"
    },
    "name": "ferc1_income_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
income_typeNoLine item name, e.g. operating_revenues (default), net_income_loss, utility_operating_expenses, depreciation_expense.
utility_typeNoSegment: total (default), electric, gas, other.

Output Schema

NameRequiredDescriptionDefault
foundNo
yearsNo
seriesNo
sourceNo
utilityNo
currencyNo
data_as_ofNo
attributionNo
income_typeNo
utility_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds useful scope facts — coverage starts in 1994, one utility per call, a default line item — but says nothing about how gaps in a utility's filing history are represented or what happens when the utility is unknown.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the identity and temporal scope of the result before the routing hint. Every clause carries information; nothing is redundant.

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 and parameter docs are complete, so the description only needs to convey scope and defaults, which it does. Minor residual gap: handling of missing years or unknown utilities is unexplained, which matters for a time-series tool.

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 schema already documents utility (name or numeric id), income_type examples, and utility_type segments. The description restates the default for income_type without adding format or behavior detail beyond the schema, so the baseline applies.

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 the exact resource (a single FERC Form 1 income-statement line, default operating_revenues), the unit of observation (one utility), and the scope (every report year on file, 1994 to date). That combination makes it tellable apart from ferc1_income_statement, which it explicitly names, though the verb ('returns') is left implicit rather than stated.

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?

It conveys the use case ('for trends') and routes the agent elsewhere for a sub-task ('Use ferc1_income_statement to see the available income_type names'). It does not state exclusions, e.g. what to use when a full multi-line statement is wanted rather than a single series, so it stops short of a full when/when-not treatment.

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.