Skip to main content
Glama
JustlyAI

DocketBird MCP Server

by JustlyAI

docketbird_search_cases

Read-onlyIdempotent

Search all indexed court cases by name or number to find DocketBird IDs, check litigation history, or verify if a company has been sued. Supports date and court filters.

Instructions

Search ALL cases in DocketBird's index by case name or case number.

Research scope: this covers every court and every case DocketBird knows
about — not just cases on your account (that's docketbird_list_cases).

Matching: case-number-shaped queries (e.g. '2:2017-bk-00112' or
'17-bk-112') match on filing year, case type, and terminating digits;
anything else matches against case names.

Date filters match in tiers: cases with an exact filing date match at day
precision; cases with only a known filing year match at year granularity;
cases with no known date are included unless exclude_unknown_dates=True.

When to use:
- Finding a case's DocketBird ID from a name or number
- Checking whether a company has been sued (pair with
  docketbird_ask_litigation_graph for who represented whom)

Args:
    query: Case name (e.g. 'Immedia Semiconductor') or case number
           (e.g. '4:2022-cv-04775'). Max 500 chars.
    court_id: Comma-separated court restriction; each entry may be a slug
              ('nysd'), an abbreviation ('S.D.N.Y.'), or a full court name.
    filed_after: Only cases filed on/after this date (YYYY-MM-DD, inclusive).
    filed_before: Only cases filed on/before this date (YYYY-MM-DD, inclusive).
    exclude_unknown_dates: Drop cases whose filing date and year are both
                           unknown from date-filtered results (default False).
    size: Results per page (default 25, max 50).
    cursor: Pagination cursor from a previous response's next-page note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNo
queryYes
cursorNo
court_idNo
filed_afterNo
filed_beforeNo
exclude_unknown_datesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Adds significant behavioral detail beyond annotations: research scope (all courts), matching logic for case numbers vs names, date filter tier behavior, and pagination via cursor. No contradictions with readOnlyHint, idempotentHint, etc.

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?

Well-structured with summary, bullet points for scope/matching/dates, when-to-use, and Args. Every sentence is informative and no redundancy.

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?

Complete given 7 params, 1 required, output schema exists. Covers all parameters, behavior, scope, matching, date filtering, pagination, and usage guidance. No gaps.

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?

With 0% schema coverage, description fully compensates by explaining each parameter: query (max 500 chars), court_id (formats), date params (inclusive, format), exclude_unknown_dates, size (bounds), cursor. Adds meaning beyond schema defaults.

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 clearly states it searches ALL cases by name or number, and explicitly distinguishes from sibling tool docketbird_list_cases which only covers user's account. The verb 'Search' and resource 'cases' are specific.

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?

Provides a 'When to use' section with two concrete use cases and suggests pairing with docketbird_ask_litigation_graph. Not explicitly stating when not to use, but the guidance is clear and helpful.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JustlyAI/docketbird-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server