Skip to main content
Glama

California Court Deadlines

by com.calcourtdeadlines
OverviewDiscussionsAdmin

California criminal pretrial motion deadlines

california_criminal_motion_deadlines
Read-only

Compute the California Rule of Court 4.111 briefing chain for a criminal pretrial motion: service of the moving papers, the proof of service, opposition, reply, and the hearing. Also gives the outside deadline for motions that run from a triggering event, such as the Penal Code section 995 motion and the section 1510 tracks. There is no service-method extension in criminal motions; rule 4.111 does not provide one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoWhether you are bringing the motion or responding.
motionYesWhich motion. pc-995 = Motion to set aside the information or indictment (§ 995); pc-1510-outside-deadline = Deadline to preserve pretrial writ review of a § 995 or § 1538.5 denial, felony (§ 1510); pc-1510-outside-deadline-misdemeanor = Deadline to preserve pretrial writ review of a § 995 or § 1538.5 denial, misdemeanor (§ 1510); pc-1424 = Motion to recuse the district attorney (§ 1424); pc-1538-5-prelim = Motion to suppress at the preliminary hearing (§ 1538.5(f)); pc-1538-5-special-hearing = Special suppression hearing in superior court (§ 1538.5(i)); pitchess-criminal = Pitchess motion, criminal (Evid. Code § 1043(a)(2)); pc-1054-5-compel = Motion to compel criminal discovery (§ 1054.5(b)); pc-1054-7-disclosure = Reciprocal discovery disclosure deadline (§ 1054.7); pc-1050-continuance = Motion to continue (§ 1050(b)); pc-1049-prepare = Time to prepare for trial (§ 1049); crc-4-110-information = Information after a holding order (CRC 4.110)
hearing_dateYesThe hearing date. For the section 1538.5(i) special hearing, this is instead the date notice was given to the People, because that clock runs forward.
trigger_dateNoFor a motion timed from an event, the date of that event (for a section 995 motion, the date of arraignment on the information).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / motion / description
      Previous value: -"Which motion. pc-995 = Motion to set aside the information or indictment (§ 995); pc-1510-outside-deadline = Deadline to preserve pretrial writ review of a § 995 or § 1538.5 denial, FELONY (§ 1510); pc-1510-outside-deadline-misdemeanor = Deadline to preserve pretrial writ review of a § 995 or § 1538.5 denial, MISDEMEANOR (§ 1510); pc-1424 = Motion to recuse the district attorney (§ 1424); pc-1538-5-prelim = Motion to suppress at the preliminary hearing (§ 1538.5(f)); pc-1538-5-special-hearing = Special suppression hearing in superior court (§ 1538.5(i)); pitchess-criminal = Pitchess motion, criminal (Evid. Code § 1043(a)(2)); pc-1054-5-compel = Motion to compel criminal discovery (§ 1054.5(b)); pc-1054-7-disclosure = Reciprocal discovery disclosure deadline (§ 1054.7); pc-1050-continuance = Motion to continue (§ 1050(b)); pc-1049-prepare = Time to prepare for trial (§ 1049); crc-4-110-information = Information after a holding order (CRC 4.110)"New value: +"Which motion. pc-995 = Motion to set aside the information or indictment (§ 995); pc-1510-outside-deadline = Deadline to preserve pretrial writ review of a § 995 or § 1538.5 denial, felony (§ 1510); pc-1510-outside-deadline-misdemeanor = Deadline to preserve pretrial writ review of a § 995 or § 1538.5 denial, misdemeanor (§ 1510); pc-1424 = Motion to recuse the district attorney (§ 1424); pc-1538-5-prelim = Motion to suppress at the preliminary hearing (§ 1538.5(f)); pc-1538-5-special-hearing = Special suppression hearing in superior court (§ 1538.5(i)); pitchess-criminal = Pitchess motion, criminal (Evid. Code § 1043(a)(2)); pc-1054-5-compel = Motion to compel criminal discovery (§ 1054.5(b)); pc-1054-7-disclosure = Reciprocal discovery disclosure deadline (§ 1054.7); pc-1050-continuance = Motion to continue (§ 1050(b)); pc-1049-prepare = Time to prepare for trial (§ 1049); crc-4-110-information = Information after a holding order (CRC 4.110)"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint=false, so the real value is the rule-specific context: the description pins behavior to Rule 4.111 and proactively rules out service-method extensions, which is a substantive constraint an agent could otherwise assume. It doesn't cover error behavior when trigger_date is omitted for event-timed motions.

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?

Three sentences, front-loaded with the primary output and then the secondary deadline family, with the service-method caveat last. No filler, though the final sentence is a caveat that could be tighter.

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?

A read-only computation tool with no output schema, so the description must convey what comes back; it does so by listing the computed deadline items. The §995/§1510 trigger-date dependency is alluded to but not tied explicitly to the trigger_date parameter, a minor gap.

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 baseline is 3; the schema already explains motion enums, hearing_date's dual meaning for §1538.5(i), and trigger_date. The description corroborates the trigger-date concept (event-timed motions like §995) but adds no format or edge-case detail beyond the schema.

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 (compute) and a specific resource/scope (the CRC 4.111 briefing chain for a criminal pretrial motion), enumerating the outputs: moving papers service, proof of service, opposition, reply, hearing. The criminal framing and rule citation distinguish it from the civil sibling california_motion_deadlines.

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?

Makes clear the tool covers two families of computation: the 4.111 briefing chain and the outside deadlines triggered by an event (§995, §1510). It also flags a when-not condition by stating there is no service-method extension in criminal motions. It stops short of explicitly routing the agent away from the civil sibling.

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

All California Court Deadlines 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