Skip to main content
Glama
oktopeak

lawmatics-mcp

by oktopeak

list-events

List events or appointments with filtering, sorting, and pagination. Filter by start_date using >= to retrieve events within a date range.

Instructions

List events (appointments) with optional filter, sort, and pagination. For a date range, filter_by: 'start_date' with filter_with: '>=' (one filter per request; sort by start_date and paginate for windows).

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.
Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It mentions the one-filter-per-request limitation and suggests pagination for date windows, which adds useful context. However, it does not discuss response format, rate limits, or any side effects, leaving some behavioral aspects undisclosed.

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, front-loaded with the core purpose, and every clause adds value. The specific guidance about date range is concise and actionable without extraneous detail.

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

Completeness4/5

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

The tool has 8 parameters, no required fields, no output schema, and no annotations. The description gives a key usage pattern and the schema covers parameter details. While it doesn't mention fetch_all, fields selection, or return values, the schema fills those gaps, making the overall context reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 88% (high), so baseline is 3. The description adds value by tying filter_by, filter_with, start_date, sort_by, and pagination together into a concrete pattern, giving operational meaning beyond the schema's individual parameter descriptions.

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 events/appointments with optional filter, sort, and pagination. It uses a specific verb and resource ('List events'), and distinguishes from sibling tools like list-activities by specifying appointments.

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?

It provides a concrete usage scenario for date ranges: filter_by 'start_date' with filter_with '>=', sort by start_date, and paginate for windows. This gives clear context for when to use these parameters, though it does not explicitly discuss when not to use this tool or name alternatives.

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