Form5500

Form5500 Schedule

form5500_schedule

Read-onlyIdempotent

Schedule H (large plan) or Schedule I (small plan) financial line items for a retirement / benefit plan, looked up by employer EIN + plan number (+ plan year) with no Ack ID needed. Returns employer, participant and total contributions, income, benefits paid, administrative expenses, assets and liabilities, plus every stored DOL line by its DOL column name. Source: U.S. Department of Labor, EBSA, Form 5500 Schedule H/I datasets (stored copy; data_as_of and loaded plan years in every response). Omit plan_year for all stored years, newest first. A plan that filed a Form 5500-SF has neither schedule.

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": {
      "ein": "261501877",
      "plan_year": 2024,
      "plan_number": "001"
    },
    "name": "form5500_schedule"
  }
}

Input Schema

Name	Required	Description
`ein`	Yes	Employer Identification Number (9 digits, dashes optional).
`plan_year`	No	Plan year (e.g. 2022). Omit for every stored plan year.
`plan_number`	Yes	Three-digit plan number (e.g. "001"; "1" is accepted).

Output Schema

Name	Required	Description
`ein`	No
`note`	No
`count`	No
`source`	No
`plan_year`	No
`schedules`	No
`data_as_of`	No
`plan_number`	No
`schedule_status`	No	h \| i \| not_loaded_year \| no_schedule_found \| store_unavailable
`loaded_plan_years`	No
`schedule_status_reason`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that data comes from a stored DOL EBSA copy, that data_as_of and loaded plan years are included in every response, and that omitting plan_year returns all stored years newest first. It also explains an important limitation: plans that filed Form 5500-SF have neither Schedule H nor Schedule I. This is substantial behavioral context for a read-only lookup tool.

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?

The description is front-loaded with the core purpose and lookup method, then adds return contents, source, and edge-case behavior. Every sentence contributes useful selection or invocation context, and there is no filler.

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?

For a three-parameter, read-only lookup with an output schema and full parameter schema coverage, the description is complete: it covers purpose, lookup key, return contents, data source, plan-year behavior, and the Form 5500-SF exception. An agent has enough information to select and invoke it correctly.

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 baseline is 3, but the description adds useful semantics beyond the schema: it frames EIN + plan number + plan year as the lookup key, states that no Ack ID is needed, and explains the omission behavior for plan_year. It does not add format details beyond what the schema already provides.

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 resource and scope: Schedule H/I financial line items for a retirement or benefit plan, looked up by EIN + plan number and optionally plan year. It also distinguishes the lookup from filing-level tools by noting that no Ack ID is needed, so an agent can identify what this tool does 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?

The description gives clear context for use, including the EIN + plan number (+ plan year) lookup pattern and the rule to omit plan_year to retrieve all stored years newest first. It also notes that Form 5500-SF filers have neither schedule, which helps exclude inapplicable cases. However, it does not explicitly name sibling alternatives such as form5500_filing or form5500_search.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Form5500 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.