Skip to main content
Glama

Ferc1 Balance Sheet

ferc1_balance_sheet
Read-onlyIdempotent

FERC Form 1 comparative balance sheet (Schedule 110) for one utility and report year: assets and liabilities/equity line items with starting and ending balances in US dollars. 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_balance_sheet"
  }
}

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.

Output Schema

NameRequiredDescriptionDefault
foundNo
assetsNo
sourceNo
utilityNo
currencyNo
headlineNo
data_as_ofNo
attributionNo
liabilitiesNo
report_yearNo
assets_countNo
years_availableNo
liabilities_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: what the payload contains (assets and liabilities/equity line items with starting and ending balances), the unit (US dollars), and provenance (FERC Form 1 via Catalyst Cooperative PUDL). It does not mention row-volatility, statement structure, or pagination, so it stops 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.

Conciseness5/5

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

Two sentences, front-loaded with what the tool returns, followed by a compact provenance note. No filler, and the source attribution earns its place by signalling data lineage and units.

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 an output schema present and 100% parameter coverage, the description only needed to establish the resource, scope, units and source — all of which it does. The one remaining gap is routing guidance toward the sibling statement tools or the utility-id resolver.

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 100%: both parameters carry descriptions, including the default-year behavior and the utility_id_ferc1 lookup hint. The description only restates the utility+year scope, adding nothing about formats or edge cases beyond the schema — baseline 3 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 a specific resource — the FERC Form 1 comparative balance sheet (Schedule 110) — and pins its scope to one utility and one report year, which cleanly separates it from siblings such as ferc1_income_statement or ferc1_utility_plant. It lacks an explicit retrieval verb, but the resource naming is precise enough for an agent to know what it returns.

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?

Scope is implied (one utility, one report year) but there is no explicit when-to-use, when-not-to-use, or alternative routing. The pointer to ferc1_find_utility for id lookup lives in the schema, not the description, so guidance is only implicit.

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.