ServiceTitan MCP

dispatch_forms_list

Read-onlyIdempotent

Search dispatch forms by ID, name, publication status, active state, triggers, conditional logic, or date range. Get a page of form metadata to locate specific form definitions.

Instructions

Search dispatch form definitions by IDs, name, publication status, active state, conditional logic, triggers, and date ranges. Returns one page of form metadata; use dispatch_form_submissions_list for completed or pending submissions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	No	Comma-separated form IDs (maximum 50)
`name`	No	Filter by form name
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, CreatedOn, ModifiedOn, Name
`active`	No	Filter by active status	True
`status`	No	Filter by form publication status
`pageSize`	No	Records per page (default 50)
`hasTriggers`	No	Filter forms by trigger usage
`includeTotal`	No	Include total count in response
`createdBefore`	No	Return forms created before this UTC timestamp
`modifiedBefore`	No	Return forms modified before this UTC timestamp
`createdOnOrAfter`	No	Return forms created on or after this UTC timestamp
`modifiedOnOrAfter`	No	Return forms modified on or after this UTC timestamp
`hasConditionalLogic`	No	Filter forms by conditional logic usage

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.0.0Sep 6, 2026

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, and open-world behavior. The description adds the useful runtime behavior that it returns one page of form metadata, which informs pagination expectations without contradicting the 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?

Two sentences carry all necessary information: the first defines scope, the second adds pagination behavior and the sibling alternative. There is no filler or redundant restatement.

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?

Given the detailed 14-parameter schema, 100% schema coverage, output schema presence, and safety annotations, the description covers the behavioral essentials not in structured fields: the single-page nature and the correct sibling for submissions. Nothing critical 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% and every parameter has a clear description and type/default/enum where relevant. The description's mention of filter categories mostly restates the schema, so it adds little parameter meaning beyond a helpful summary.

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 opens with the specific verb 'Search' and the resource 'dispatch form definitions', then enumerates the key filter dimensions (IDs, name, status, active, conditional logic, triggers, date ranges). It also distinguishes itself from dispatch_form_submissions_list, so an agent can differentiate the tool without opening the schema.

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?

It clearly scopes use to searching form definitions and explicitly routes submission-related lookups to dispatch_form_submissions_list. This gives an agent a concrete when-to-use/when-not-to-use decision.

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

Deploy Server