Skip to main content
Glama

Ferc1 Find Utility

ferc1_find_utility
Read-onlyIdempotent

Find FERC Form 1 respondents (US investor-owned electric/gas utilities that file the annual FERC Form 1) by name. Returns the FERC respondent id to use in the other ferc1_* tools. found:false when no respondent matches.

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": {
      "query": "PacifiCorp"
    },
    "name": "ferc1_find_utility"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax matches to return (default 20, max 100).
queryYesPart of the utility name, e.g. "PacifiCorp" or "duke energy".

Output Schema

NameRequiredDescriptionDefault
countNo
foundNo
queryNo
sourceNo
utilitiesNo
data_as_ofNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety behavior is covered structurally. The description adds one genuinely useful behavioral detail beyond that – 'found:false when no respondent matches' – but says nothing about ambiguity when several utilities share a name fragment or how the limit truncates results.

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?

Three short sentences, front-loaded with what is searched and what is returned, ending with the no-match convention. There is no filler and no restatement of the title.

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 full schema coverage, the description needn't restate return fields; it still flags the found:false case and the downstream id usage, which is what an agent needs to chain calls. The only gap is handling of multiple/ambiguous matches.

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%, with both query (name fragment) and limit (default 20, max 100) documented in the schema itself. The description only reinforces that matching is by name and adds no syntax, casing, or ranking semantics, so the baseline 3 applies.

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?

States a specific verb and resource ('Find FERC Form 1 respondents'), defines the population (US investor-owned electric/gas utilities filing the annual form), and scopes matching to name. It also positions itself as the resolver that feeds the other ferc1_* tools, so an agent can tell it apart from the data-retrieval siblings.

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?

Explicitly says the returned FERC respondent id is what you use in the other ferc1_* tools, which gives clear call-ordering guidance (resolve first, then fetch). It doesn't state any when-not conditions or what to do instead if multiple matches return, but the intended workflow is unambiguous.

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.