Weave
Sign InSign Up
View as .md ↗
Lawmatics

Lawmatics | List Sub Statuses

MCP server · Practice Management · lawmatics.com · 40 categories · 177 tools

Lawmatics is a legal CRM, client intake, and marketing automation platform for law firms. This integration exposes contacts, companies, matters, billing (invoices, transactions, expenses, time entries), tasks, documents, events, and marketing data as governed MCP tools, scoped per member by access level.

lawmatics_list-sub-statuses

List matter sub statuses from Lawmatics with optional pagination, filtering, and sorting. Filterable by name (string) or created_by_id (numeric id). Rows carry a `relationships` envelope with a to-one {id,type} pointer to the creating user; use get-sub-status for the full envelope including the matters (prospects) carrying each sub status.

Tool Input

pageinteger— Page number (1-based)(> 0)
filterobject— Optional single-field filter; one filter at a time
fieldstringrequired— Field to filter on: name (string); created_by_id (numeric id); status (matter outcome label — hired, pnc, or lost — mapped to its documented integer code; exact-case match required)(enum: "name", "created_by_id", "status")
operatorstring— Comparison operator. name: = != like ilike null not_null. created_by_id: = != < <= > >= null not_null. status: = != null not_null only (ordering on codes not offered). Omit for the Lawmatics per-field default(enum: "=", "!=", "<", "<=", ">", ">=", "like", "ilike", "null", "not_null")
valuestring— Value to compare against. Required for the comparison operators; must be omitted for the null / not_null presence operators. For created_by_id, must be a non-negative integer. For status, must be exactly one of: hired, pnc, lost (lowercase, case-sensitive) — mapped to its integer code before sending
sortBystring— Column to sort by(enum: "id", "created_at", "updated_at", "name", "status")
sortOrderstring— Sort direction; ascending or descending(enum: "asc", "desc")

Tool Output

subStatusesarrayrequired— Sub statuses on this page of results
[]object
idstringrequired— Lawmatics sub status ID
namestringrequired— Sub status name
statusstringrequired— Matter status this sub status maps to; one of "hired", "pnc", or "lost"
createdAtstringrequired— When the sub status was created, as an ISO 8601 timestamp
updatedAtstringrequired— When the sub status was last updated, as an ISO 8601 timestamp
relationshipsobjectrequired— To-one JSON:API relationship pointers as {id,type} stubs. Not materialized — follow a pointer by calling that resource's own tool (type 'user' -> get-user). List rows carry to-one pointers only; use get-sub-status for the full envelope incl. the to-many `prospects` pointers.
1 field
createdByobjectnullrequired— Creating user pointer; null when unset
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
paginationobjectnullrequired— Pagination metadata from the API response; null when the endpoint returns no meta envelope
totalPagesnumbernullrequired— Total number of pages available; null if not reported
limitPerPagenumbernullrequired— Maximum sub statuses returned per page; null if not reported
totalEntriesnumbernullrequired— Total number of sub statuses across all pages; null if not reported

We're Adding More Lawmatics Tools Constantly!

Don't see a specific Lawmatics tool you need? Email [email protected] and we can add it.

Lawmatics Frequently Asked Questions

What does the List Sub Statuses tool do?

This page documents the List Sub Statuses tool (lawmatics_list-sub-statuses). List matter sub statuses from Lawmatics with optional pagination, filtering, and sorting. Filterable by name (string) or created_by_id (numeric id). Rows carry a relationships envelope with a to-one {id,type} pointer to the creating user; use get-sub-status for the full envelope including the matters (prospects) carrying each sub status. It is one of the Lawmatics Sub Statuses tools, invoked through your firm's Weave MCP connection and available to members whose access level permits it.

What is the Lawmatics integration?

The Lawmatics integration connects your firm's Lawmatics account to Weave. Lawmatics is a legal CRM, client intake, and marketing automation platform for law firms. This integration exposes contacts, companies, matters, billing (invoices, transactions, expenses, time entries), tasks, documents, events, and marketing data as governed MCP tools, scoped per member by access level. It groups 177 tools into 40 categories, exposed through your firm's Weave MCP connection and filtered per member by access level.

How does my firm connect Lawmatics to Weave?

An admin connects Lawmatics once for the whole firm via OAuth. Every member then works through that single connection; there is no per-user Lawmatics login.

Do I need to install or configure anything locally?

No. Weave is fully hosted, so there is nothing to install, run, or maintain on your own machines. An admin connects Lawmatics once from the Weave console through a secure OAuth handshake, and your credentials are encrypted at rest and stay inside Weave's infrastructure. After that, each member simply points their AI assistant at your firm's Weave MCP endpoint, and the tools they are allowed to use appear automatically based on their access level.

Can everyone on my team use every tool?

No. Tools are exposed per member by access level, so each person only sees the Lawmatics tools their role permits.

Are changes made through these tools reversible?

Reads are always safe. Deletes are irreversible: they remove the record from Lawmatics permanently.

How are money amounts represented?

All monetary values (expenses, transactions, invoices, time-entry rates) are integer cents; for example, 50000 means $500.00.

Related Tools

List MattersList StagesList Practice Areascreate-sub-statusdelete-sub-statusget-sub-status