ServiceTitan MCP

dispatch_arrival_windows_list

Read-onlyIdempotent

List arrival-window definitions page by page, filtered by active state or creation time. See each configured window and applicable business units to identify the record you need.

Instructions

List one page of arrival-window definitions, optionally filtered by active state or creation time. Each record supplies a configured window and applicable business units; use dispatch_arrival_windows_get for a known ID.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Page number (starts at 1)
`active`	No	Filter by active status	True
`pageSize`	No	Records per page (default 50)
`includeTotal`	No	Include total count in response
`createdBefore`	No	Return items created before this UTC timestamp
`createdOnOrAfter`	No	Return items created on or after this UTC timestamp

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv3.0.0Sep 6, 2026

removedInput schema / properties / modifiedBefore

Removed value: -{
-  "description": "Return items modified before this UTC timestamp",
-  "format": "date-time",
-  "type": "string"
-}

removedInput schema / properties / modifiedOnOrAfter

Removed value: -{
-  "description": "Return items modified on or after this UTC timestamp",
-  "format": "date-time",
-  "type": "string"
-}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

First observedv2.5.1Apr 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds useful context beyond annotations: paginated one-page behavior, filterable by active state or creation time, and the fact that each record includes a configured window and business units.

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 tightly packed sentences with no filler. The core action and filters are front-loaded, and the second sentence adds record content plus the routing alternative, all earning their place.

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

Completeness5/5

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

Complete for a paginated list tool: it covers purpose, filtering options, record contents, and the correct sibling for known-ID retrieval. With output schema available and annotations covering safety, nothing essential is missing.

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 100%, so the schema already documents every parameter. The description summarizes filters as 'active state or creation time' but adds no deeper meaning beyond what parameter descriptions already provide, so baseline 3 is appropriate.

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?

States a specific verb ('List') and resource ('arrival-window definitions'), with clear scope: one page, optional filters, and record content. It explicitly distinguishes itself from dispatch_arrival_windows_get by directing known-ID lookups to that sibling.

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

Usage Guidelines5/5

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

Gives an explicit alternative and the condition for using it: 'use dispatch_arrival_windows_get for a known ID.' This tells the agent when not to use this list tool and where to route instead.

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

Deploy Server