create_case

The general-purpose tool for creating cases. It accepts the same payload as POST /v3/api/cases and runs through the same handler — an MCP call and a REST call with the same body behave identically. This page lists the fields so the MCP section stands alone; the REST page carries the deeper narrative and response examples.

The schema is strict: unknown fields are rejected, not ignored, and every problem in a payload comes back at once, each with a field path.

Top-level fields

Recipient

Document

Exactly one of url, content, or documentId must be set per document. For a case built around a single library template, create_case_from_document is the simpler call.

Settings

Example call

{
  "title": "Consulting agreement — Q3",
  "recipients": [
    { "name": "Jane Jensen", "email": "jane@example.com" }
  ],
  "documents": [
    { "name": "Agreement.pdf", "url": "https://example.com/agreement.pdf" }
  ],
  "settings": { "expiresInDays": 14 }
}

Result

The tool returns JSON. On success, the same case object as the REST endpoint — id, state, recipients with delivery status, documents, and any notices:

{
  "case": {
    "id": "665f1c2ab4d746b7bb394001",
    "title": "Consulting agreement — Q3",
    "state": "open",
    "recipients": [ { "name": "Jane Jensen", "delivery": { "email": "sent" } } ]
  }
}

On failure the result is marked as an error and explains itself:

{
  "error": "validation-failed",
  "details": [
    { "field": "recipients.0.email", "message": "recipient email is required" }
  ]
}

A malformed payload that doesn't match the schema at all is rejected by the protocol layer as an invalid params error before the tool runs — same information, different envelope.

Related