Bankruptcy Observer

List cases by industry

get_cases_by_industry_tool

Read-onlyIdempotent

US business bankruptcy cases by industry label or key (Hotels, Retail, real-estate, etc.). Individual debtors and adversary proceedings (lawsuits) are omitted unless include_individuals or include_adversary is true. start_date and end_date are inclusive calendar days (YYYY-MM-DD). When a date is set, total is the full match count and skip (or offset) pages past limit (max 100). Filings from the last two days often have no NAICS yet; those are listed in untagged_recent instead of being dropped. debtorCity is the city only. Paid.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "industry": "<industry>"
    },
    "name": "get_cases_by_industry_tool"
  }
}

Input Schema

Name	Required	Description
`skip`	No	Rows to skip. Alias: offset. skip wins when both are set.
`limit`	No	Max rows in this page (1-100). Default 25.
`offset`	No	Alias for skip.
`end_date`	No	Filed on or before this date (YYYY-MM-DD), inclusive through the end of that day.
`industry`	Yes	Industry label or key, for example Hotels or Retail.
`start_date`	No	Filed on or after this date (YYYY-MM-DD), inclusive of that whole day.
`include_adversary`	No	Include adversary proceedings (lawsuits). Default false.
`include_individuals`	No	Include individual debtors. Default false (business filings only).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026
- addedInput schema / properties / industry / description
```
Added value: +"Industry label or key, for example Hotels or Retail."
```

Changed7 schema fields changedOct 7, 2026

addedInput schema / properties / end_date / description

Added value: +"Filed on or before this date (YYYY-MM-DD), inclusive through the end of that day."

addedInput schema / properties / include_adversary

Added value: +{
+  "description": "Include adversary proceedings (lawsuits). Default false.",
+  "type": "boolean"
+}

addedInput schema / properties / include_individuals

Added value: +{
+  "description": "Include individual debtors. Default false (business filings only).",
+  "type": "boolean"
+}

addedInput schema / properties / limit / description

Added value: +"Max rows in this page (1-100). Default 25."

addedInput schema / properties / offset

Added value: +{
+  "description": "Alias for skip.",
+  "type": "integer"
+}

addedInput schema / properties / skip

Added value: +{
+  "description": "Rows to skip. Alias: offset. skip wins when both are set.",
+  "type": "integer"
+}

addedInput schema / properties / start_date / description

Added value: +"Filed on or after this date (YYYY-MM-DD), inclusive of that whole day."

AddedJun 5, 2026
RemovedJun 3, 2026
Changed12 schema fields changedJun 2, 2026
- removedInput schema / properties / end_date / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / end_date / default
```
Removed value: -null
```
- removedInput schema / properties / end_date / title
```
Removed value: -"End Date"
```
- addedInput schema / properties / end_date / type
```
Added value: +"string"
```
- removedInput schema / properties / industry / title
```
Removed value: -"Industry"
```
- removedInput schema / properties / limit / default
```
Removed value: -25
```
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- removedInput schema / properties / start_date / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / start_date / default
```
Removed value: -null
```
- removedInput schema / properties / start_date / title
```
Removed value: -"Start Date"
```
- addedInput schema / properties / start_date / type
```
Added value: +"string"
```
- removedInput schema / title
```
Removed value: -"get_cases_by_industry_toolArguments"
```

Changed1 schema field changedMar 12, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_cases_by_industry_toolOutput",
-  "type": "object"
-}New value: +null

First observedMar 11, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Beyond the annotations, it discloses important behavior: individual debtors and adversary proceedings are omitted by default, date bounds are inclusive, pagination uses total/skip/offset with a max limit of 100, recent filings may appear in untagged_recent, and the tool is paid. These details materially affect invocation and result interpretation.

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 dense but front-loaded with purpose and key caveats, and most sentences carry useful information. The unexplained debtorCity sentence is the main piece that does not clearly earn its place.

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?

For an 8-parameter, paid list tool with no output schema, the description covers the key invocation caveats and mentions response quirks like total and untagged_recent. It is nearly complete, though explicit sibling routing and clearer return-value context would make it stronger.

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 the schema already documents all eight parameters. The description adds modest clarification around inclusive dates and pagination, but the orphaned note that “debtorCity is the city only” references neither an input parameter nor a clearly identified output field.

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?

The description states a specific verb+resource: US business bankruptcy cases filtered by industry label or key, with examples. It is clear what the tool returns, but it does not explicitly distinguish itself from siblings such as get_cases_by_naics_tool or get_cases_by_date_range_tool.

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?

The description implies usage by explaining industry filtering and omission defaults, but it gives no explicit when-to-use guidance versus alternative tools. An agent must infer that this is the right choice when filtering by industry label rather than NAICS, state, or date range.

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

All Bankruptcy Observer 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.