Skip to main content
Glama

Ferc1 Utility Plant

ferc1_utility_plant
Read-onlyIdempotent

FERC Form 1 summary of utility plant and accumulated provisions for depreciation, amortization and depletion (Schedule 200) for one utility and report year: plant in service, construction work in progress, accumulated depreciation, by segment, in US dollars.

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

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
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.6/5.0
Behavior3/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 context beyond that: scope is a single respondent and a single report year, rows are broken out by segment, and values are in US dollars. It stops short of saying what happens when the utility name is ambiguous or no data exists for the year.

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?

A single front-loaded sentence with the key framing (schedule, scope) before the field list; every clause carries information. It is dense and jargon-heavy for one sentence, but nothing is redundant.

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 a fully described 3-parameter schema, an output schema, and annotations covering safety and idempotency, the description needs only to establish what the tool returns and at what granularity, which it does. Nothing an agent needs in order to call it 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?

Schema description coverage is 100%, so all three parameters are already documented in detail, including the year default and the utility_id_ferc1 alternative. The description only echoes the utility/year scope and hints at the segment dimension through 'by segment', adding little beyond the schema. Baseline 3 is appropriate.

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?

Names a specific resource (FERC Form 1 utility plant / Schedule 200) with a stated scope of one utility and one report year, and enumerates the line items returned (plant in service, CWIP, accumulated depreciation). That is enough to separate it from siblings like ferc1_balance_sheet or ferc1_income_statement, though it never explicitly contrasts itself with them.

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 is only implied by the scope phrase 'for one utility and report year'; there is no explicit when-to-use statement and no when-not or alternative routing in the description itself. The pointer to ferc1_find_utility lives in the schema, not the description, so the agent gets no guidance at the description level.

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.