Skip to main content
Glama

Find a company's court cases by business name

search_cases_by_business
Read-only

Cases with a COMPANY as a party — by business name.

Use this, not search_cases_by_party, whenever the subject is an organization: an LLC, corporation, insurer, hospital, landlord, dealership or municipality. Party search requires a first AND last name, which a business does not have, so it cannot answer this at all.

FAST — about 5-45 seconds. No CAPTCHA. Do not warn about a long wait.

EVERY ROW NOW CARRIES case_status, with no enrich needed — so do not call lookup_court_case merely to find out whether a case is open or closed. The returned text is FINER-GRAINED than the four filter values: alongside "Pending" and "Disposed" you will see "Disposed - Voluntary Dismissal", "Disposed - Dismissal on Order of the Court", "Disposed - Clerk of Superior Court" — i.e. HOW it ended, not just that it did. So never test it with equality against the filter vocabulary (status == "Disposed" misses most disposed rows); match on a prefix, and quote the portal's own wording when you report it.

TYPE THE NAME AS IT APPEARS, COMMA INCLUDED. The comma is significant and NARROWING: "FOOD LION, LLC" is a different, smaller search than "FOOD LION". Do not strip it, and do not replace it with a wildcard — advice to do that appears in the portal's help text but applies to a different search mode.

WILDCARD: a trailing * is allowed and needs AT LEAST 4 characters before it. "WALM*" works; "WAL*" is rejected. Use it for a company whose exact registered name you do not know ("CAROLINA TOWING*").

THERE IS NO PARTY ROLE IN THIS RESULT, ON PURPOSE. The portal labels every row "Defendant" regardless of the truth — including cases the company FILED as plaintiff and criminal cases where it was the victim. NEVER say the business is the defendant. Read the side from case_name ("X VS Y" — the company's position in the caption is the real signal), or call lookup_court_case for the actual party list.

THE 200-CASE CAP BITES IMMEDIATELY FOR ANY CHAIN OR INSURER. results_truncated: true means real matches are MISSING. Worse, county filters AFTER that cap, so a truncated county-filtered count is a LOWER BOUND, never a total — "11 cases in Wake" may be 11 of the 200 statewide the portal was willing to show. Only case_status and the file-date range narrow server-side. Say the list is incomplete instead of reporting a count as if it were complete.

matched_businesses lists the distinct entity names actually hit. More than one means legally separate entities are mixed together ("FOOD LION, LLC" alongside "DELHAIZE AMERICA, LLC") — surface that rather than treating them as one company.

Dates: ISO YYYY-MM-DD or MM/DD/YYYY — both accepted. These bound WHEN THE CASE WAS FILED, not when anything is scheduled. A year at a time is the most effective way to get a chain's cases under the 200-cap: 'FOOD LION' unfiltered caps out, but restricted to 2023 it returns 42 complete rows.

Public record. Read-only. North Carolina (NC) only. Informational, not legal advice.

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": {
      "name": "<name>"
    },
    "name": "search_cases_by_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe business name, written as the user wrote it — "FOOD LION, LLC" is a narrower search than "FOOD LION". For a PERSON use search_cases_by_party instead.
limitNo
countyNo
case_statusNo
file_date_endNo
file_date_startNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"The business name, written as the user wrote it — \"FOOD LION, LLC\" is a narrower search than \"FOOD LION\". For a PERSON use search_cases_by_party instead."
    • addedInput schema / properties / name / examples
      Added value: +[
      +  "FOOD LION, LLC",
      +  "DUKE ENERGY"
      +]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint; the description supplies the behavior that actually matters: 5-45s latency with no CAPTCHA, a hard 200-case cap where results_truncated:true means missing matches, the fact that county filters AFTER the cap (so counts are lower bounds), that no party role is returned on purpose and 'Defendant' labels are unreliable, and that matched_businesses may mix legally separate entities. This is far beyond what the annotations disclose.

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?

Front-loaded with purpose, then usage, then behavior — correct ordering. It is long, but each paragraph encodes a distinct failure mode (cap, county post-filter, party-role trap, comma significance) rather than padding. Heavy all-caps emphasis and slightly episodic ordering keep it from a 5.

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 6-parameter, open-world search with a 200-row truncation hazard, the description covers routing, latency, filter semantics, returned fields, and count reliability. The output schema exists, yet the description still clarifies what results_truncated and matched_businesses MEAN, which is semantic rather than redundant.

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

Parameters5/5

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

Schema description coverage is only 17%, so the description carries the load and does: the comma in the name is significant and narrowing, wildcards require a trailing `*` with 4+ characters, dates accept ISO or MM/DD/YYYY and bound the FILING date (not scheduling), and case_status returns finer-grained values than the four-value enum so equality matching fails. That directly compensates for the near-empty schema.

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?

Opens with a precise verb+resource+scope: 'Cases with a COMPANY as a party — by business name.' It immediately distinguishes itself from the sibling it resembles, stating that search_cases_by_party requires a first AND last name and therefore 'cannot answer this at all.' An agent can route correctly without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use routing: organizations (LLC, corporation, insurer, hospital, landlord, dealership, municipality) go here, persons go to search_cases_by_party. It also pre-empts two tempting mistakes — calling lookup_court_case just to learn open/closed status, and calling it to recover party roles. When/when-not is fully covered.

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.

Resources