Skip to main content
Glama

Form5500 Filing

form5500_filing
Read-onlyIdempotent

Get Form 5500 filing detail from the DOL EFAST2 index. Pass ack_id for a single filing (sponsor, plan name/number, participant counts, begin/end-of-year plan assets, plan type, filing date, and full filing PDF URL). Pass ein instead to get a plan sponsor's full filing history (all Form 5500 filings for that EIN, newest first). For an ack_id the response also carries the plan's Schedule H (large plans) or Schedule I (small plans) financial line items - employer / participant / total contributions, income, benefits paid, expenses, assets and liabilities - from the U.S. Department of Labor, EBSA, Form 5500 Schedule H/I datasets (stored copy, data_as_of stated), under schedule_h or schedule_i. schedule_status is always one of h, i, not_filed_sf (5500-SF filers file neither schedule), full_form_no_schedule, not_loaded_year, not_in_dataset_yet, unknown_plan_year, store_unavailable - never a silent null. Schedule C service providers are not included; pdf_url links to the complete filing.

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": {
      "ack_id": "20181015141633P030269394337001"
    },
    "name": "form5500_filing"
  }
}

Input Schema

NameRequiredDescriptionDefault
einNoEmployer Identification Number (9 digits, dashes optional). Returns the full filing history for that employer.
limitNoFor ein history: max filings to return (1-200, default 50).
ack_idNoEFAST2 Acknowledgement ID (the 30-char filing id, e.g. "20230407122300NAL0001820321001"). Returns one filing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "ack_id": "20230407122300NAL0001820321001"
      -  },
      -  {
      -    "ein": "942679060",
      -    "limit": 50
      -  }
      -]New value: +[
      +  {
      +    "ack_id": "20181015141633P030269394337001"
      +  },
      +  {
      +    "ack_id": "20230407122300NAL0001820321001"
      +  },
      +  {
      +    "ein": "942679060",
      +    "limit": 50
      +  }
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses the data source, that schedule data comes from a stored copy with data_as_of, and that schedule_status is never a silent null but one of several enumerated states. It also clarifies exclusions, such as Schedule C not being included, and that pdf_url points to the complete filing.

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?

The description is front-loaded with the core purpose and the two parameter modes. It is dense and somewhat long, but most detail is useful because there is no output schema and the schedule_status enumeration prevents ambiguity.

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 no output schema, the description carries the full burden of explaining return values and does so thoroughly: filing fields, history ordering, schedule H/I financial line items, schedule_status values, and the Schedule C exclusion. Nothing essential for correct invocation appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents the inputs. The description still adds meaningful outcome semantics by explaining exactly what ack_id returns, what ein history returns and in what order, and how schedule_h/schedule_i and schedule_status relate to those parameters.

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: get Form 5500 filing detail from the DOL EFAST2 index. It clearly separates the two operating modes, ack_id for a single filing and ein for full filing history, so an agent can distinguish this from broader search or schedule-focused 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?

It gives explicit usage for the two primary parameters: pass ack_id for one filing or ein for a sponsor's full history. It also notes that Schedule C service providers are not included and that pdf_url links to the complete filing, though it does not explicitly name sibling alternatives such as form5500_search.

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.