Skip to main content
Glama

CaseMagic — Federal Court Case Lookup & Monitor

by io.github.sustany
OverviewDiscussionsAdmin

Get deadlines and dates the docket sets

get_case_deadlines
Read-onlyIdempotent

Return the dates a federal docket states — "Responses due by 10/14/2026", "Hearing set for 3/2/2027" — each quoted verbatim with the entry that states it and how many days away it is, plus a small set of deadlines CaseMagic computes from the Federal Rules where the triggering event is on the docket and the rule is the same nationwide: the time to move after a judgment (FRCP 59/50/52) and the time to file a notice of appeal (FRAP 4(a)). Every computed date shows the rule, the day count and a caveat, and is never phrased as an instruction to file. CaseMagic still does not compute deadlines that depend on a district's local rules or a judge's standing orders — most motion-response and discovery windows — so a deadline a local rule implies but the docket does not state will not appear. An empty result means nothing is stated or computable, not that the user has none. Identify the case with case_number (and court, if known), or with matter_id for a case already saved to the account. No account is needed to give a case number. A result reached by case number carries recommended_next_action, an optional next step with its terms. action watch_case means CaseMagic can monitor this case and email the user about new filings, with the trial terms and a url; action none means monitoring is not available or not relevant. Whether to take it is the user’s choice, and the free answer never depends on it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
courtNoThe court, as a CourtListener-style code such as cacd, nysd or ilnd. Optional: leave it out when the user does not know which district the case is in.
matter_idNoThe 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.
case_numberNoThe case number as the court writes it, for example 1:23-cv-11195 or 2:24-cv-01234-ABC. Judge initials are optional and are ignored when matching.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseNoThe case: court, case number, caption, filing date, status, judges, nature of suit, latest activity and docket size.
as_ofNoWhen the calculation was made.
basisNoWhat the dates are based on.
errorNoPresent only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
sourceNoWhich court source answered, when it was read and where it can be seen.
case_urlNoThe case’s public page on CaseMagic, which offers free email alerts and Watch.
computedNoDeadlines computed from the Federal Rules, each with rule, day count and caveat.
deadlinesNoUpcoming dates the docket states, each quoted with its entry and days away.
matter_idNoThe account matter id when the case was read through a saved case; null for a lookup.
disclaimerNoWhat the dates are not.
not_includedNoWhat is deliberately not computed.
connect_tokenNoShort-lived token for create_case_passport, present on a lookup by case number.
docket_coverageNoHow much of the court docket CaseMagic holds for this case.
recently_passedNoStated dates that have just passed.
what_comes_nextNoOne sentence on where to send a user who wants to hear about new filings.
recommended_next_actionNoThe offer to make after answering, decided by the server: action watch_case when the case is open and can be monitored, none otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "as_of": {
+      "description": "When the calculation was made."
+    },
+    "basis": {
+      "description": "What the dates are based on.",
+      "type": "string"
+    },
+    "case": {
+      "additionalProperties": true,
+      "description": "The case: court, case number, caption, filing date, status, judges, nature of suit, latest activity and docket size.",
+      "properties": {
+        "assigned_judge": {
+          "description": "Assigned judge."
+        },
+        "case_name": {
+          "description": "Caption.",
+          "type": "string"
+        },
+        "case_number": {
+          "description": "Case number as the court writes it.",
+          "type": "string"
+        },
+        "case_status": {
+          "description": "open, terminated, or null when the source does not say."
+        },
+        "cause": {
+          "description": "Cause of action."
+        },
+        "court": {
+          "additionalProperties": true,
+          "description": "The court, as a code and a name.",
+          "properties": {
+            "code": {
+              "description": "Court code, e.g. nysd.",
+              "type": "string"
+            },
+            "name": {
+              "description": "Court name.",
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "docket_entry_count": {
+          "description": "How many entries the court docket has."
+        },
+        "filing_date": {
+          "description": "ISO date the case was filed."
+        },
+        "id": {
+          "description": "CaseMagic id of the court case.",
+          "type": "string"
+        },
+        "latest_activity_at": {
+          "description": "ISO timestamp of the latest docket activity."
+        },
+        "nature_of_suit": {
+          "description": "Nature of suit."
+        },
+        "referred_judge": {
+          "description": "Referred magistrate judge."
+        },
+        "terminated_date": {
+          "description": "ISO date the case was terminated, or null while it is open."
+        }
+      },
+      "type": "object"
+    },
+    "case_url": {
+      "description": "The case’s public page on CaseMagic, which offers free email alerts and Watch.",
+      "type": "string"
+    },
+    "computed": {
+      "description": "Deadlines computed from the Federal Rules, each with rule, day count and caveat.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "connect_token": {
+      "description": "Short-lived token for create_case_passport, present on a lookup by case number.",
+      "type": "string"
+    },
+    "deadlines": {
+      "description": "Upcoming dates the docket states, each quoted with its entry and days away.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "disclaimer": {
+      "description": "What the dates are not.",
+      "type": "string"
+    },
+    "docket_coverage": {
+      "additionalProperties": true,
+      "description": "How much of the court docket CaseMagic holds for this case.",
+      "properties": {},
+      "type": "object"
+    },
+    "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 account matter id when the case was read through a saved case; null for a lookup."
+    },
+    "not_included": {
+      "description": "What is deliberately not computed."
+    },
+    "recently_passed": {
+      "description": "Stated dates that have just passed.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "recommended_next_action": {
+      "additionalProperties": true,
+      "description": "The offer to make after answering, decided by the server: action watch_case when the case is open and can be monitored, none otherwise.",
+      "properties": {
+        "action": {
+          "description": "watch_case or none.",
+          "type": "string"
+        },
+        "card_required": {
+          "description": "Whether a card is collected for the trial.",
+          "type": "boolean"
+        },
+        "cta": {
+          "description": "Button text.",
+          "type": "string"
+        },
+        "guidance": {
+          "description": "How to make the offer.",
+          "type": "string"
+        },
+        "offer": {
+          "description": "What monitoring does.",
+          "type": "string"
+        },
+        "plans": {
+          "description": "The three plans with price and how many cases each covers.",
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "price_after_trial": {
+          "description": "Price of the entry plan after the trial.",
+          "type": "string"
+        },
+        "reason": {
+          "description": "Why, in a sentence the assistant can repeat.",
+          "type": "string"
+        },
+        "suggested_message": {
+          "description": "One sentence the assistant may say, once.",
+          "type": "string"
+        },
+        "trial_days": {
+          "description": "Free trial length in days.",
+          "type": "number"
+        },
+        "url": {
+          "description": "Where the user starts watching this case.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "source": {
+      "additionalProperties": true,
+      "description": "Which court source answered, when it was read and where it can be seen.",
+      "properties": {
+        "name": {
+          "description": "Source name.",
+          "type": "string"
+        },
+        "retrieved_at": {
+          "description": "ISO timestamp of the read."
+        },
+        "url": {
+          "description": "Link to the docket at the source."
+        }
+      },
+      "type": "object"
+    },
+    "what_comes_next": {
+      "description": "One sentence on where to send a user who wants to hear about new filings.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Well beyond the readOnly/idempotent/openWorld annotations, it discloses that computed dates carry the rule, day count and a caveat, are never phrased as filing instructions, and that an empty result means nothing is stated or computable rather than none exist. It also explains the recommended_next_action contract and the watch_case monitoring offer, which annotations cannot convey.

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 the core purpose and the stated-vs-computed distinction, and nearly every clause carries distinct information. It is dense and long with several em-dash asides, so it is not maximally tight, but there is little true 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?

With an output schema present, return values need not be explained, and the description still covers identification modes, the boundary of computed deadlines, empty-result semantics, and the optional next-action path. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: court is optional when the district is unknown, matter_id applies to already-saved cases, and no account is needed to supply a case number. These usage nuances go beyond the per-field schema text.

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?

States a specific verb and resource ('Return the dates a federal docket states') and immediately scopes it with verbatim examples and the bounded set of CaseMagic-computed dates. It clearly distinguishes stated docket dates from rule-computed deadlines, so an agent can tell it apart from siblings like get_case_docket or get_case_status 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 Guidelines4/5

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

Gives clear conditions of use: identify by case_number (plus court if known) or matter_id, and it explicitly states when computed deadlines do and do not appear (local-rule and standing-order windows are excluded). It stops short of naming a specific sibling alternative for those excluded cases, which keeps it from a 5.

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 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