CaseMagic — Federal Court Case Lookup & Monitor

Read the whole docket of a saved case

get_case_docket

Read-onlyIdempotent

Return every docket entry CaseMagic holds for a saved case, newest first, each with the court's own wording and the documents filed with it: the main filing and its attachments, how many pages each has, whether a free PDF can be opened, and how much of its text can be read. Use this when the user wants to go through the whole case, find a particular filing, or ask about anything older than the last few entries; get_case_passport carries only the most recent twenty. Each document carries a document_id to pass to read_case_document for its text. The payload says how many entries the court docket has in all, so a docket CaseMagic is still reading is never mistaken for a complete one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_case_docket"
  }
}

Input Schema

Name	Required	Description
`limit`	No	How many entries to return. Defaults to 200.
`offset`	No	How many entries to skip, newest first. Defaults to 0.
`matter_id`	No	The CaseMagic matter id, as returned by create_case_passport or shown in an earlier result. Omit it when the account follows exactly one case and that is the one meant.

Output Schema

Name	Required	Description
`error`	No	Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
`offset`	No	Where this page starts.
`entries`	No	Docket entries with their documents.
`matter_id`	No	The case.
`next_offset`	No	Where the next page starts, or null at the end.
`entries_held`	No	Entries CaseMagic holds.
`coverage_note`	No	What is held and what is still to come.
`documents_note`	No	Where documents come from.
`whole_docket_read_at`	No	When the whole docket was last read.
`entries_on_court_docket`	No	Entries the court docket has.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "coverage_note": {
+      "description": "What is held and what is still to come.",
+      "type": "string"
+    },
+    "documents_note": {
+      "description": "Where documents come from.",
+      "type": "string"
+    },
+    "entries": {
+      "description": "Docket entries with their documents.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "entries_held": {
+      "description": "Entries CaseMagic holds.",
+      "type": "number"
+    },
+    "entries_on_court_docket": {
+      "description": "Entries the court docket has."
+    },
+    "error": {
+      "additionalProperties": true,
+      "description": "Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.",
+      "properties": {
+        "code": {
+          "description": "Machine-readable error code, for example CASE_NOT_FOUND or MULTIPLE_CASES_FOUND.",
+          "type": "string"
+        },
+        "message": {
+          "description": "What went wrong, in a sentence.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "matter_id": {
+      "description": "The case.",
+      "type": "string"
+    },
+    "next_offset": {
+      "description": "Where the next page starts, or null at the end."
+    },
+    "offset": {
+      "description": "Where this page starts.",
+      "type": "number"
+    },
+    "whole_docket_read_at": {
+      "description": "When the whole docket was last read."
+    }
+  },
+  "type": "object"
+}

AddedSep 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: newest-first ordering, the document_id handoff to read_case_document, and the completeness signal that the payload reports the court's total entry count so a still-loading docket isn't mistaken for a full one. It does not cover pagination semantics for limit/offset or any auth prerequisites, keeping it short of a 5.

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 scope and page-shape come first, then the when-to-use rule and the sibling contrast, then the follow-up tool and the completeness caveat, each sentence carrying distinct information. It is dense and long for a single description, but no sentence is wasted.

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?

Even though an output schema exists and return values needn't be spelled out, the description summarizes the payload shape and its completeness caveat. Combined with the sibling routing and parameter coverage, an agent has everything needed to invoke this correctly.

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 limit, offset and matter_id in detail. The description reinforces newest-first ordering and the document_id linkage but adds no syntax, format, or constraint detail beyond what the schema provides. Baseline 3 is appropriate.

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 names a specific verb and resource ('Return every docket entry CaseMagic holds for a saved case') plus the scope of what comes back (court wording, documents, page counts, PDF availability, extractable text). It explicitly distinguishes itself from the sibling get_case_passport by noting that tool 'carries only the most recent twenty.'

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?

It states the when-to-use conditions directly ('when the user wants to go through the whole case, find a particular filing, or ask about anything older than the last few entries') and names the alternative with the exact boundary that selects it. It also routes follow-up to read_case_document for text, so both the 'use this' and 'use that instead' paths are covered.

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

All CaseMagic — Federal Court Case Lookup & Monitor 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.

Resources

Need Help?