Skip to main content
Glama

Ferc1 Purchased Power

ferc1_purchased_power
Read-onlyIdempotent

FERC Form 1 purchased power and exchanges (Schedule 326) for one utility and report year, 1994 to date: each seller (counterparty), purchase type (RQ requirements, LF long-term firm, IF intermediate firm, SF short-term firm, LU long-term unit, OS other/non-firm, EX exchange, AD adjustment), MWh purchased and settlement dollars. Rows sorted by MWh, subtotal rows excluded and reported separately. Answers "who did PacifiCorp buy the most power from in 1994". 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": 1994,
      "utility": "PacifiCorp"
    },
    "name": "ferc1_purchased_power"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoReport year (e.g. 2023). Default: the latest year on file for the respondent.
limitNoMax rows to return (default 25, max 200).
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.
purchase_typeNoOptional purchase type code filter, e.g. OS, LF, LU, RQ.

Output Schema

NameRequiredDescriptionDefault
noteNo
rowsNo
foundNo
sourceNo
messageNo
utilityNo
currencyNo
ambiguousNo
row_countNo
candidatesNo
data_as_ofNo
attributionNo
report_yearNo
detail_mwh_sumNo
years_availableNo
copy_refreshed_atNo
subtotals_excludedNo
top_counterparties_aggregatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: rows are sorted by MWh descending in effect, subtotal rows are excluded and "reported separately," and coverage starts in 1994. Slight ambiguity remains about where subtotals are reported, but overall this is useful 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 what the tool returns, followed by behavioral detail and provenance; nothing is padded. The first sentence is heavily packed with the full code enumeration, which slightly hurts scannability but every clause carries information.

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 an output schema present, the description need not explain return shapes, and it still covers grain, sort order, subtotal handling, date range and source provenance. The utility-identifier lookup path is documented in the schema via ferc1_find_utility, so an agent has everything needed to call it correctly.

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%, so the baseline is 3 and the schema already documents utility, year, limit and purchase_type. The description does expand the purchase-type codes (RQ, LF, IF, SF, LU, OS, EX, AD) with human-readable meanings that the schema only sketches with examples, which is marginal added value rather than new calling mechanics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — FERC Form 1 purchased power and exchanges (Schedule 326) — plus the exact grain (one utility, one report year, 1994 to date) and the per-row fields (counterparty, purchase type, MWh, settlement dollars). It is clearly the purchase-side counterpart to sibling tools like ferc1_sales_for_resale and ferc1_income_statement, so an agent can distinguish it without opening the schema.

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 gives a concrete triggering question ("who did PacifiCorp buy the most power from in 1994") and states the one-utility/one-year constraint, which shapes how the agent should call it. It stops short of explicit exclusions or naming alternatives, though the purchase-side framing implicitly separates it from sales-for-resale and income tools.

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.