Skip to main content
Glama

List matters

clio_list_matters
Read-onlyIdempotent

Retrieve a list of legal matters from Clio Manage with filters for status, client, practice area, and free-text search.

Instructions

Lists matters with optional filtering. Use query for free-text search across matter names, client_id to scope to a single client, and status to filter by lifecycle stage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoMatter status. Clio enums are case-sensitive.
client_idNoNumeric Clio contact id of the client.
practice_area_idNo
responsible_attorney_idNo
queryNoFree-text search across matter names and descriptions.
updated_sinceNoISO 8601 timestamp — return matters updated after this time.
fieldsNoOverride the default fields list. Default: id,display_number,description,status,open_date,close_date,pending_date,practice_area{id,name},client{id,name,type},responsible_attorney{id,name},originating_attorney{id,name},billable,billing_method
limitNoMax records to return across all pages. Capped by CLIO_MAX_PAGE_SIZE.
page_sizeNoRecords per Clio API page (default from CLIO_DEFAULT_PAGE_SIZE).
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds behavioral context: case-sensitive enums, pagination caps, default fields. No contradictions.

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?

Two sentences: first states core purpose, second provides actionable parameter guidance. No wasted words, front-loaded with key intent.

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?

Given 9 parameters, high schema coverage, no output schema, and annotations, the description covers filtering, pagination, and case-sensitivity. It could mention output is a list, but implied. Complete enough for a read-only list tool.

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 high (78%). The description explains the purpose of key parameters (query, client_id, status) and mentions case-sensitivity, adding value beyond schema. Some parameters like practice_area_id are not explained.

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 a specific verb-resource pair ('Lists matters') and distinguishes from siblings like clio_get_matter. It lists optional filtering parameters, clearly indicating the scope.

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 provides explicit guidance on when to use certain parameters (query, client_id, status) but does not contrast with sibling tools like clio_get_matter or clio_search_contacts. It implies usage for listing matters with filters.

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/patrickking67/clio-manage-mcp'

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