Skip to main content
Glama

Docket Nexus

by com.docketnexus
OverviewDiscussionsAdmin

Cases involving a company

get_company_cases
Read-onlyIdempotent

List public cases linked to a company, newest or oldest first, optionally filtered by nature of suit or court. Paginate with next_cursor. At most 25 per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesDocket Nexus company slug, as used by get_company.
sortNoOrder by case filing date. 'newest' (default) or 'oldest'.newest
courtNoFilter to one court as shown on the company page (e.g. 'District Court, N.D. Alabama').
limitNoCases to return, 1-25. Defaults to 25.
cursorNoOpaque pagination token from a previous call's next_cursor. Omit for the first page.
nature_of_suitNoFilter to one nature-of-suit category as shown on the company page (e.g. 'Product Liability').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / court / description
      Added value: +"Filter to one court as shown on the company page (e.g. 'District Court, N.D. Alabama')."
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque pagination token from a previous call's next_cursor. Omit for the first page."
    • addedInput schema / properties / limit / description
      Added value: +"Cases to return, 1-25. Defaults to 25."
    • addedInput schema / properties / nature_of_suit / description
      Added value: +"Filter to one nature-of-suit category as shown on the company page (e.g. 'Product Liability')."
    • addedInput schema / properties / slug / description
      Added value: +"Docket Nexus company slug, as used by get_company."
    • addedInput schema / properties / sort / description
      Added value: +"Order by case filing date. 'newest' (default) or 'oldest'."
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "newest",
+  "oldest"
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds meaningful behavioral constraints: only public cases, sorting order, optional filters, pagination via next_cursor, and a maximum of 25 results per call.

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?

Two sentences with no wasted words. The core purpose is front-loaded, followed by filtering, sorting, and pagination constraints, all essential for correct invocation.

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?

The description covers purpose, filters, sorting, pagination, and result limits. Since there is no output schema, it could ideally describe the shape of returned case items, but the sibling get_case tool and the phrase 'List public cases' make the usage reasonably complete.

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 six parameters. The description summarizes sort, court/nature_of_suit filters, cursor, and limit, but adds no meaning beyond what the schema 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 verb and resource: 'List public cases linked to a company.' It also adds sorting, filtering, and pagination details that clearly distinguish it from siblings like get_company, get_case, and search_cases.

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 makes clear when to use it: when you need public cases for a specific company slug, with optional filters and pagination. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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

All Docket Nexus toolsInspect
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.

Resources