Skip to main content
Glama
oktopeak

lawmatics-mcp

by oktopeak

list-pipelines

Retrieve law firm pipelines with matter counts, estimated value, and stage references to build a complete pipeline board view.

Instructions

List the firm's pipelines with matter counts, estimated value, and stage references. Use with list-stages to build a full pipeline board view.

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 must carry the full burden of behavioral disclosure. It only mentions the output fields and a companion usage, but does not disclose pagination behavior, default limits, read-only nature, or any side effects. The two sentences add little beyond what the tool's name implies.

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 consists of exactly two sentences, both of which carry useful information: the first states the primary purpose and output, and the second gives a practical cross-reference. There is no fluff or repetition of schema content.

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 tool has 8 parameters and no output schema or annotations. The description gives a clear purpose and a companion tool reference, which helps an agent decide when to use it. However, it lacks details about return structure, pagination defaults, or how the parameters interact (e.g., filter behavior), making it only minimally adequate given the tool's complexity.

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%, which is high, so the baseline is 3. The description itself does not add parameter-level meaning beyond the schema; the phrase 'stage references' hints at stage_id but does not clarify any specific parameter. The schema already explains each parameter in detail, so no penalty.

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's purpose: 'List the firm's pipelines with matter counts, estimated value, and stage references.' This is a specific verb+resource pairing (list pipelines) with scope ('firm's') and defines the return content, distinguishing it from sibling list-* tools like list-stages.

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 explicitly says 'Use with list-stages to build a full pipeline board view,' providing a concrete use case and naming a companion tool. This counts as clear context, though it doesn't state when NOT to use this tool or list alternative approaches.

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