Court Rules

Use this when the user has a draft court filing and wants to compare it with a judge's filing rules before filing it. The tool checks page and word limits, format, required sections, and privacy redactions, and it reports whether courtesy copies and a pre-motion conference are required. It supports only judges in courts with the following `district_id` values: edny. Get the `judge_slug` from search_judges. Read the draft yourself and pass what you measured. The required inputs are `judge_slug`, `district_id`, `document_scope`, `is_pro_se`, `pmc_completed`, `opposing_party_pro_se`, `filing_role`, and `document`, and inside `document` only `page_count` and `word_count` are required. Count body pages only, and leave out the cover, tables of contents and authorities, signature page, and certificates. The optional blocks of `document` are `caption`, `signature_block`, `sections`, `format`, and `privacy`, and each block must be filled in completely or left out entirely. Pass a block only when you can fill every field in it, because a guessed value can produce a wrong PASS or FAIL. When you leave a block out, the tool skips its checks and lists them in `warnings`. For a filing that isn't part of a motion, omit `motion_type`, set `filing_role` to "movant", and set `pmc_completed` to false. Each result names the rule it comes from in `source`, and each PASS or FAIL covers only the facts you passed. To read a judge's rules without a draft, use get_judge_rules.

check_filing_against_judge_rules

Use this when the user wants the complete set of rules extracted from one judge's standing orders and individual practices documents, and you have the judge's `district_id` and `judge_slug` (from list_courts and search_judges). It returns every extracted rule for that judge, and each rule includes its quoted source text and source URL. For a specific topic, including one judge's page limits or courtesy copies, use search_filing_rules. To show the rules to the user in a panel, use open_judge_rules_panel.

get_judge_rules

Use this when you have an enforcement action's ID or slug (from search_privacy_enforcement_actions) and you need its full record, which includes the laws cited, statute sections, remedies, other enforcers, source quotes, and document URLs. It returns one action. To find actions, use search_privacy_enforcement_actions.

get_privacy_enforcement_action

Use this when the user asks for counts of recorded privacy enforcement actions, or for total recorded fines, grouped by jurisdiction, violation type, risk level, or month. It returns one row per group with the number of actions and the total fines, within an optional date range, and it also returns the number of distinct actions. A settlement that several states reported counts once in total fines. To list matching actions, or to count the matches for a set of filters, use search_privacy_enforcement_actions. To read the full record of one action, use get_privacy_enforcement_action.

get_privacy_enforcement_stats

Use this when the user asks whether a court is closed on a date, or when the user wants a court's holiday and closure dates. It returns each recorded holiday's date and name, with the URL of the court page that lists it and the date the page was last checked. A date with no record isn't confirmed open. Pass `district_id` (from list_courts) to answer for one court, and narrow the results with `year`, or with `date_from` and `date_to`. The tool doesn't calculate filing deadlines.

list_court_holidays

Use this when you need a court's `district_id`, or when you want to know which courts are covered. It returns each court's name, its `district_id`, and the number of judges who currently sit there. There are many courts, so pass `query` with part of a court name or ID (for example "alaska", "edny", or "superior") to find one court. Results come in pages, so call the tool again with `offset` set to the previous `next_offset`. The last page has a null `next_offset`. To find judges, use search_judges, and to find rules, use search_filing_rules.

list_courts

Use this when the user asks to see or browse a judge's filing rules and the client can show a panel. It opens a panel that lists the judge's rules by type, and each rule appears with its quoted source text and a link to the source document. Pass both the `district_id` and the `judge_slug` returned by search_judges, or pass neither to open the panel on a judge search. The result names the judge and doesn't include rule text, so use get_judge_rules when you need to read or quote the rules yourself.

open_judge_rules_panel

Use this when the user asks about a specific topic in the filing rules of a court or of a judge, such as electronic filing, service and proof of service, filing timing, fees, courtesy copies, page limits, or rejection and cure windows. It also finds a court's own rules when you set `judge_slug` to "court", and it covers both state and federal courts. It returns structured rule summaries, and each summary includes the quoted source text, the citation, and the source URL. Narrow the search with `district_id`, `judge_slug`, `logic_type`, `workflow_phase`, `case_type`, or words in `q`. A field that a rule leaves out isn't stated in the source quote, so don't infer a default or a negative value. To read the complete set of rules for one known judge, use get_judge_rules.

search_filing_rules

Use this when you need a judge's `judge_slug` for another tool, or when the user asks which judges sit in a court. It returns each judge's name, `judge_slug`, type, `district_id`, and status. Filter by `district_id` and by part of the judge's `name`, and use `judge_type` to narrow the list further. The search leaves out judges who no longer appear on a court's published list of judges, unless `include_inactive` is true. For a large court, pass `district_id` (from list_courts) so the list of matches stays short. To read a judge's rules, use get_judge_rules.

search_judges

Use this when the user asks about privacy or consumer data protection enforcement by the FTC, a state attorney general, or another regulator, such as who was fined, for what, and when. It returns the matching actions with the most recent first, and each action includes its date, jurisdiction, entity, fine amount, violation types, risk level, summary, and source links. The response also gives the total number of matches. Filter by `jurisdiction`, `date_from` and `date_to`, `industry`, `violation_type`, `entity_name`, or `risk_level`. For the laws cited, remedies, and source quotes of one action, use get_privacy_enforcement_action, and for counts and total fines grouped by a field, use get_privacy_enforcement_stats. The tool doesn't cover court filing rules, judges, or court holidays.

search_privacy_enforcement_actions