Skip to main content
Glama
oktopeak

lawmatics-mcp

by oktopeak

list-practice-areas

List your firm's practice areas from Lawmatics, returning each area's ID, name, and color. Use filters, sorting, and pagination to target specific records.

Instructions

List the firm's practice areas (id, name, color).

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, and the description does not disclose behavioral traits such as pagination limits, default sorting, or read-only nature. It simply states that it lists practice areas, leaving the agent to infer behavior from the schema.

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 a single sentence that directly states the tool's purpose with no extraneous words, earning high marks for conciseness and structure.

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?

For a tool with 8 optional parameters and no output schema, the description is overly minimal. It doesn't mention advanced capabilities like filtering, pagination, or sorting, which the schema includes. An agent would need to inspect the schema fully to understand the tool's potential.

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%, so the schema already explains most parameters. The description adds minimal value by hinting that the default output includes id, name, and color, but this does not significantly enrich parameter meaning beyond what the schema provides.

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 uses the specific verb 'List' and identifies the resource as 'the firm's practice areas', with the parenthetical indicating the returned fields. This clearly distinguishes it from sibling list tools like list-matters or list-contacts.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It merely states what the tool does without context for agent decision-making.

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