Skip to main content
Glama
Sign In
Clio Manage MCP

Clio Manage MCP

by patrickking67
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List calendar entries

clio_list_calendar_entries
Read-onlyIdempotent

Retrieve law firm calendar entries by specifying a date range. Optionally filter by calendar or matter to narrow results.

Instructions

Lists calendar entries within a date range. Use ISO dates (YYYY-MM-DD).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "clio_list_calendar_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesStart of range, YYYY-MM-DD (inclusive).
toYesEnd of range, YYYY-MM-DD (inclusive).
calendar_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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description does not need to restate safety. The description adds date format context, but beyond that, no behavioral traits (e.g., pagination, return format) are disclosed. Adequate but not rich.

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 of 9 words, efficiently stating the purpose and a key format rule. No wasted text.

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?

The description is minimal for a tool with 6 parameters and no output schema. Missing information about pagination, return value structure, and behavior beyond date range. Relies heavily on schema annotations.

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 67% (4 of 6 parameters described). The description adds 'ISO dates (YYYY-MM-DD)' which is already covered by schema descriptions for 'from' and 'to'. It does not compensate for undocumented parameters (calendar_id, matter_id). Marginal addition.

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 'Lists calendar entries within a date range' uses a specific verb and resource, clearly distinguishing from siblings like clio_list_calendars (which lists calendars) and clio_create_calendar_entry.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a basic guideline on date format ('Use ISO dates (YYYY-MM-DD)'), but does not explicitly state when to use this tool versus alternatives or provide exclusion criteria. Usage is implied.

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