Get Matter (lawmatics_get-matter)
Fetch a single matter (legal case) from Lawmatics by ID, including case details, status, contact information, matter value, custom fields, and a `relationships` envelope of {id,type} pointers to related records (contact, company, attorneys, tasks, notes, files, invoices, and more).
Tool Input
matterIdstringrequired— ID of the matter to fetch; a numeric string (e.g. '25')(pattern: ^\d+$)
Tool Output
idstringrequired— Lawmatics matter ID
caseTitlestringnullrequired— Title of the matter/case; null if unset
caseBlurbstringnullrequired— Short description of the matter; null if unset
statusstringrequired— Matter status (e.g. "pnc", "hired", "lost", "active")
subStatusstringnullrequired— Sub-status label within the status; null if unset
firstNamestringnullrequired— First name of the matter's primary contact; null if unset
lastNamestringnullrequired— Last name of the matter's primary contact; null if unset
middleNamestringnullrequired— Middle name of the contact; null if unset
namePrefixstringnullrequired— Name prefix of the contact (e.g. Mr, Ms, Dr); null if unset
nameSuffixstringnullrequired— Name suffix of the contact (e.g. Jr, Sr, III); null if unset
informalNamestringnullrequired— Informal name / nickname of the contact; null if unset
emailstringnullrequired— Primary email address of the matter's contact; null if unset
phonestringnullrequired— Primary phone number of the matter's contact; null if unset
emailAddressstringnullrequired— Primary email address record value (mirrors email); null if unset or not reported
phoneNumberstringnullrequired— Primary phone number record value (mirrors phone); null if unset or not reported
addressstringnullrequired— Combined display address of the contact; null if unset or not reported
birthdatestringnullrequired— Contact's date of birth; null if unset
agenumbernullrequired— Contact's age in years, derived from birthdate; null if unknown or not reported
genderstringnullrequired— Contact's gender as stored; null if unset
maritalStatusstringnullrequired— Contact's marital status; null if unset
citizenshipstringnullrequired— Contact's citizenship; null if unset
timezonestringnullrequired— Contact's time zone; null if unset
employerstringnullrequired— Contact's employer; null if unset
occupationstringnullrequired— Contact's occupation; null if unset
titlestringnullrequired— Contact's job title; null if unset
biostringnullrequired— Free-text biography of the contact; null if unset
hobbiesstringnullrequired— Contact's hobbies as stored; null if unset
socialSecuritystringnullrequired— Contact's social security number; null if unset
driverLicensestringnullrequired— Contact's driver license number; null if unset
referringUrlstringnullrequired— URL the contact was referred from; null if unset
estimatedValueCentsnumbernullrequired— Estimated value of the matter in integer cents; null if unset
actualValueCentsnumbernullrequired— Actual value of the matter in integer cents; null if unset
leadCostCentsnumbernullrequired— Cost of acquiring this lead in integer cents; null if unset
dateOfLastContactstringnullrequired— When the contact was last contacted, as an ISO 8601 timestamp; null if never or not reported
daysSinceLastContactnumbernullrequired— Days since the contact was last contacted; null if unknown or not reported
photoUrlstringnullrequired— Absolute URL of the contact's photo; null when none is set or not reported
customFieldsarrayrequired— Account-defined custom fields on the matter; empty array if none
[]object
idstringrequired— Custom field definition ID, as a numeric string
namestringnullrequired— Custom field display name; null if unset
fieldTypestringnullrequired— Custom field data type (e.g. text, date, select); null if unset
valueanyrequired— Raw custom field value; type varies by `fieldType`
formattedValueanyrequired— Display-formatted custom field value; type varies by `fieldType`
createdAtstringrequired— When the matter was created, as an ISO 8601 timestamp
updatedAtstringrequired— When the matter was last updated, as an ISO 8601 timestamp
relationshipsobjectrequired— JSON:API relationship pointers to related records as {id,type} stubs. Not materialized — follow a pointer by calling that resource's own get/find tool (e.g. type 'contact' -> get-contact, type 'user' -> get-user).
sourceobjectnullrequired— Lead source pointer; null when unset
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
stageobjectnullrequired— Pipeline stage pointer; null when unset
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
campaignobjectnullrequired— Marketing campaign pointer; null when unset
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
practiceAreaobjectnullrequired— Practice area pointer; null when unset
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
salespersonobjectnullrequired— Salesperson (user) pointer; null when unset
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
leadAttorneyobjectnullrequired— Lead attorney (user) pointer; null when unset
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
originatingAttorneyobjectnullrequired— Originating attorney (user) pointer; null when unset
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
ownedByobjectnullrequired— Owning user pointer; null when unset
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
createdByobjectnullrequired— Creating user pointer; null when unset
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
contactobjectnullrequired— Primary contact pointer; null when unset
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
companyobjectnullrequired— Linked company pointer; null when unset
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
assignedStaffarrayrequired— Assigned staff (user) pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
eventsarrayrequired— Event pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
fileRequestsarrayrequired— File-request pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
documentsarrayrequired— Document pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
filesarrayrequired— File pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
foldersarrayrequired— Folder pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
notesarrayrequired— Note pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
tasksarrayrequired— Task pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
emailsarrayrequired— Email-address pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
phoneNumbersarrayrequired— Phone-number pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
addressesarrayrequired— Address pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
invoicesarrayrequired— Invoice pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
tagsarrayrequired— Tag pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
relationshipsarrayrequired— Related-party relationship-record pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
We're Adding More Lawmatics Tools Constantly!
Don't see a specific Lawmatics tool you need? Email support@weave.legal and we can add it.
Lawmatics Frequently Asked Questions
What does the Get Matter tool do?
This page documents the Get Matter tool (lawmatics_get-matter). Fetch a single matter (legal case) from Lawmatics by ID, including case details, status, contact information, matter value, custom fields, and a relationships envelope of {id,type} pointers to related records (contact, company, attorneys, tasks, notes, files, invoices, and more). It is one of the Lawmatics Matters 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.