Skip to main content
Glama
Sign In
Clio Manage MCP

Clio Manage MCP

by patrickking67
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List folders

clio_list_folders
Read-onlyIdempotent

Lists folders under a parent folder or top-level if no parent_id is given. Navigate document structure in Clio Manage.

Instructions

Lists folders under a parent, or top-level if no parent_id given.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clio_list_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
parent_idNo
matter_idNo
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds value by explaining the parent-child behavioral nuance. It does not contradict annotations.

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, efficient sentence with no wasted words. It conveys the essential information concisely.

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?

Given no output schema and 50% schema coverage, the description covers the core behavior but omits details about matter_id usage. It is sufficient for a simple list operation but could be more complete.

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 50% (limit and page_size described). The description adds meaning for parent_id (optionality and effect) but does not mention matter_id. Baseline at 3 because coverage is not low but incomplete.

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 that it lists folders under a parent or top-level if no parent_id given. It uses a specific verb ('Lists') and resource ('folders'), and distinguishes itself from sibling tools like clio_list_documents or clio_list_calendars.

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 clear context on when to use this tool: when listing folders, with behavior dependent on parent_id. However, it does not explicitly mention when not to use it or suggest alternatives, though among siblings, no other folder-listing tool exists.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools