Skip to main content
Glama
oktopeak

lawmatics-mcp

by oktopeak

list-forms

List intake forms from Lawmatics with pagination, filtering, and sorting. Retrieve form IDs and metadata to manage forms.

Instructions

List the firm's custom forms (intake forms). Form IDs are UUIDs. Use get-form to see a form's field structure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (Lawmatics returns a fixed 25 records per page).
fieldsNoComma-separated attributes to return, or 'all' for everything. Add 'custom_fields' to include custom field values.
sort_byNoAttribute to sort by, e.g. 'created_at', 'updated_at', 'id'. Default: id, newest first.
fetch_allNoFollow pagination and return every record (capped at 1,000). The response says complete=false if truncated.
filter_byNoAttribute to filter on. IMPORTANT: the Lawmatics API supports only ONE filter per request. Association filters use the _id suffix, e.g. practice_area_id, stage_id, source_id, matter_id, contact_id.
filter_onNoValue to filter for. Required with filter_by unless filter_with is null/not_null.
sort_orderNo
filter_withNoFilter operator: =, !=, <, <=, >, >=, like, ilike (default: ilike for text — add % wildcards for fuzzy match, e.g. %smith%), or presence checks: null, not_null. Currency values are in cents.
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only adds that forms are custom/intake forms and that form IDs are UUIDs, but it does not disclose pagination behavior, sorting/filtering capabilities, or any side effects. This is minimal behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long with no redundant information. It is front-loaded with the core action and resource, and every clause adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the basic purpose and an alternative, but with 8 parameters and no output schema, it is not fully complete. The schema covers parameter details, but the description does not mention return format or usage nuances like pagination or filtering, leaving some gaps.

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 88%, and the schema itself has detailed parameter descriptions. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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?

The description clearly states the tool lists the firm's custom forms (intake forms) with a specific verb+resource. It also distinguishes itself from get-form by pointing to that sibling for field structure, making the scope unambiguous.

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?

The description gives an explicit alternative ('Use get-form to see a form's field structure'), which is helpful for choosing between tools. However, it does not state when not to use list-forms or mention other relevant list tools, so it lacks full exclusion guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oktopeak/lawmatics-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server