UniCourt

UniCourt case document order status: poll a document-order callback started with uc_case_document_order. The uc_ prefix means UniCourt. WHEN TO USE: After uc_case_document_order returns a caseDocumentOrderCallbackId, or when the user asks for the status of an in-flight document order. Do not use this tool to start a new order — use uc_case_document_order for that. PARAMETERS: - callback_id: required 18-character caseDocumentOrderCallbackId from the uc_case_document_order response POLLING (strict): - Call about every 10-15 seconds after uc_case_document_order. - Stop immediately on COMPLETE or FAILURE. - Treat IN_PROGRESS and DELAYED as still running. - At most 10 status calls. If still not terminal after 10, tell the user to try later (they can call uc_case_document_order_status again later). Do not poll forever. After COMPLETE, use uc_case_document_view with mode=url and the caseDocumentId if a download URL is needed (for preview downloads set is_preview_document=true when appropriate). Case-search page limits do not apply here.

uc_case_document_order_status

UniCourt case document view: read one case document by UniCourt caseDocumentId — metadata (info) or a time-limited download URL (url). The uc_ prefix means UniCourt. WHEN TO USE: After uc_case_view documents / docket_*_documents sections return a caseDocumentId (18 characters). Not a court filing number. MODE: - info: document details (name, pages, price, repository, preview flags, availability, parent/child ids) - url: download payload including fileUrl and expiryDate when available OPTIONAL: is_preview_document (mode=url only) requests a preview download when a preview is available. Call mode=info and mode=url separately as needed. Case-search page limits do not apply here.

uc_case_document_view

UniCourt entity view: read party, counsel, or judge details by UniCourt entity id. The uc_ prefix means UniCourt. WHEN TO USE: After uc_case_view returns partyId, counselId, or judgeId values. entity_type: party | counsel | judge detail: overview (all); associated_counsel (party or counsel); associated_parties (counsel only) PAGINATION: associated_* list details may be paginated with page_number. You may fetch additional pages as needed so the user can see all related data. Case-search page limits do not apply here. Invalid combinations return success=false.

uc_case_entity_view

UniCourt case search: find cases in the connected UniCourt workspace using everyday language. The uc_ prefix means UniCourt. WHEN TO USE: When the user wants to locate or identify UniCourt cases (by case number, party, court, dates, or similar). q RULES (strict): - Pass the user's wording nearly verbatim as plain language. Light cleanup only (typos, obvious case-number formatting). - Do not invent a special query language. - Do not expand acronyms with synonym pairs (e.g. "OSHA or Occupational Safety and Health Act"). - Do not insert boolean logic: AND, OR, NOT, parentheses-as-grouping, &&, ||, or field operators. - If the request is ambiguous, or the user would need synonyms/boolean intent clarified, ask the user—do not invent that logic in q. - Matches are keyword/text hits, not verified labels that a claim is a confirmed cause of action. PARAMETERS: - q: plain-language search (see q RULES above) - page_number: 1 (default) or 2 only. Do not use values above 2. - sort / order: optional sort (filedDate or relevancy; asc or desc) PAGINATION RULES (strict — uc_case_search only; does not apply to uc_case_view, uc_case_entity_view, or uc_case_document_view): - Default: call once with page_number=1. Never autopaginate search results. - Call page_number=2 only if the user explicitly asks for more matches or the next page. - If the user asks for a specific page beyond 2: do not call this tool with that page. Tell them only the first two search pages are available for now, and ask them to narrow the search to identify a specific case (party, case number, court and dates, etc.), then use uc_case_view. COUNTS: - For how-many / count / total questions, use data.totalCount from the response. Do not paginate to compute a count, even when totalCount is large. WORKFLOW: 1. uc_case_search with q and page_number=1 → list matches (and totalCount) 2. Read UniCourt caseId from results, then uc_case_view / uc_case_entity_view / uc_case_document_view as needed Returns case matches including UniCourt caseId values for follow-up tools.

uc_case_search

UniCourt case update: start a refresh of a case from the court source. The uc_ prefix means UniCourt. WHEN TO USE: After you have an 18-character UniCourt caseId and the user wants fresher case data than what is already in the workspace. Call this tool once to start the update. Do not use this tool to poll progress. AFTER CALLING: Response is usually status IN_PROGRESS. Then poll with uc_case_update_status (same case_id) about every 10-15 seconds until COMPLETE or FAILURE. See uc_case_update_status for polling limits. PRIORITY: - Default priority_level is level2. Always send that unless the user explicitly asks for a different level. - Allowed values: level1, level2, level5. Change from level2 only when the user explicitly specifies the level. OPTIONAL: fetch_type (INCREMENTAL or FULL), notify_on_delay. PACER: PACER case update is not supported. Do not attempt PACER credential options; tell the user PACER case update is not supported. Case-search page limits do not apply here.

uc_case_update

UniCourt case update status: read the CaseUpdate object for a caseId (progress of a refresh started with uc_case_update). The uc_ prefix means UniCourt. WHEN TO USE: After uc_case_update returns (usually IN_PROGRESS), or when the user asks for the current update status of a case. Do not use this tool to start a new update — use uc_case_update for that. PARAMETERS: - case_id: required 18-character UniCourt caseId (same id used with uc_case_update) POLLING (strict): - Call about every 10-15 seconds after uc_case_update. - Stop immediately on COMPLETE or FAILURE. - Treat IN_PROGRESS and DELAYED as still running. - At most 10 status calls. If still not terminal after 10, tell the user to try later (they can call uc_case_update_status again later). Do not poll forever. After COMPLETE, use the nested case in the response and/or uc_case_view as needed. Case-search page limits do not apply here.

uc_case_update_status

UniCourt case view: read details for one UniCourt caseId (overview, parties, counsel, dockets, and related sections). The uc_ prefix means UniCourt. WHEN TO USE: After you have an 18-character UniCourt caseId from uc_case_search (or the user). Set section to the slice you need. SECTIONS: overview, parties, counsel, judges, hearings, related_cases, tentative_rulings, docket_entries, documents, docket_primary_documents, docket_secondary_documents. SORT: For hearings, docket_entries, and documents sections, optional sort_by must be exactly "latest to oldest" or "oldest to latest". Do not use field names (e.g. docketEntryDate) or asc/desc. PAGINATION: List sections may be paginated with page_number. You may fetch additional pages as needed so the user can see all data for that section. These search-result page limits do not apply here. For a single document's metadata or download URL, use caseDocumentId values from documents sections with uc_case_document_view. UniCourt caseId is not a court case number — resolve numbers with uc_case_search first.

uc_case_view

Return the UniCourt account selected for this signed-in UniCourt MCP session. The uc_ prefix means UniCourt.

uc_current_active_account

UniCourt normalized law firm profile (Entity Research): returns the NormLawFirm object for a normLawFirmId. The uc_ prefix means UniCourt. Tool name includes "norm" on purpose. NOT THE SAME AS CASE VIEW: - Do NOT use this for case-scoped counsel/firm names. Use this after uc_norm_law_firm_search for directory normLawFirmId (QLAW…) profiles. PARAMETERS: - norm_law_firm_id: required 18-character normLawFirmId Returns the upstream NormLawFirm payload in data. Case-search page limits do not apply here.

uc_norm_law_firm_profile

UniCourt normalized law firm search (Entity Research): find law firms in the normalized law firm directory using a structured query expression. The uc_ prefix means UniCourt. Tool name includes "norm" on purpose. NOT THE SAME AS CASE VIEW: - Do NOT use this for case-scoped counsel/firm names from a docket. For case participants use uc_case_view / uc_case_entity_view. - Use this tool when the user wants normalized law firm directory data (normLawFirmId / QLAW… ids). q IS A STRUCTURED EXPRESSION (not plain language like uc_case_search): - Unlike uc_case_search, you MUST use AND/OR/NOT and field:value syntax. - Field names are case-sensitive (normLawFirmId not normlawfirmid). - Max 15 operators in one query. q length 3–2000 characters. OPERATORS: | Operator | Example | | AND | name:(Willson) AND normLawFirmId:"QLAW811qJ0hBpbm4NH" | | OR | name:(Willson) OR normLawFirmId:"QLAW811qJ0hBpbm4NH" | | NOT | name:(Willson) NOT normLawFirmId:"QLAW811qJ0hBpbm4NH" | | "phrase" | name:"Willson Law Firm" | VALUE FORMS: field:(TOKEN) or field:"exact phrase or id" TOP-LEVEL FIELDS: normLawFirmId, name, lastFetchDate, lastFetchDateWithUpdates, lastIdEvolutionDate EXAMPLES: - normLawFirmId:"QLAW811qJ0hBpbm4NH" - name:(Willson) PARAMETERS: - q: structured expression (required unless search_id is set) - page_number: page of results (default 1; paginate as needed) - search_id: prior normLawFirmSearchId from a response — when set, paginate that search (search_id preferred over q for the HTTP call) INVALID q RETRIES (agent-side, strict): - On success=false with INVALID_INPUT / invalid query field, fix q using this guide and retry. - At most 3 total attempts (including the first). Then stop and report the error. Do not invent fields. Returns matches including normLawFirmId for follow-up. Case-search page limits do not apply here.

uc_norm_law_firm_search