Skip to main content
Glama
oktopeak

lawmatics-mcp

by oktopeak

list-companies

List companies in Lawmatics CRM with optional filtering, sorting, and pagination to find specific records or retrieve all data.

Instructions

List companies with optional filter, sort, and pagination.

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?

With no annotations, the description bears full responsibility for behavioral disclosure. It only mentions optional filter/sort/pagination but omits critical constraints like the single-filter limit, fixed page size of 25, the 1,000-record cap on fetch_all, or how results are returned. These behaviors are documented in the schema but not in the description, leaving the agent without a complete operational picture.

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?

The description is a single efficient sentence with no wasted words. It front-loads the primary action and resource. It could be more informative but is appropriately concise for a list operation.

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

Completeness2/5

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

Given the tool has 8 parameters, no output schema, and no annotations, a single-sentence description is insufficient. It fails to convey API quirks (persistent filters, pagination behavior), when to use it vs. find-company, and what the response shape might be. The schema helps but the overall tool definition remains incomplete for an agent to confidently invoke it in varied contexts.

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 each parameter has detailed descriptions within the schema. The main description adds no additional semantic value; it simply summarizes capabilities already present in the schema. Baseline of 3 is appropriate since the schema carries the load.

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 action ('List'), the resource ('companies'), and the scope of behavior (optional filter, sort, pagination). This distinguishes it from sibling tools that operate on different resources or fetch single records (e.g., get-company).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to choose this tool over alternatives such as find-company or get-company. The description does not mention scenarios, exclusions, or relationships to sibling tools.

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