ServiceTitan MCP Server

list_technician_shifts

List technician shift schedules filtered by start date range. View availability and assignments for technicians.

Instructions

List technician shift schedules.

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": "list_technician_shifts"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`page_size`	No
`starts_on_or_after`	No
`starts_on_or_before`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 11, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits but only states 'List technician shift schedules.' It does not mention read-only nature, authentication needs, pagination behavior, or any side effects. The presence of an output schema is not referenced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single-sentence description is concise but too minimal to be informative. It avoids waste but sacrifices valuable context that could be added in one or two more sentences.

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?

With four parameters, no schema descriptions, and no annotations, the description leaves significant gaps. It does not explain pagination or date filtering, and the output schema (though present) is not described. The tool is underspecified for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no meaning to the four parameters (page, page_size, starts_on_or_after, starts_on_or_before). Schema coverage is 0%, and the names are somewhat self-explanatory, but the description should at least clarify the date filter format or default behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists technician shift schedules with a specific verb and resource. However, it does not differentiate from many sibling list tools beyond the resource name, missing context on how shifts differ from appointments or bookings.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like list_bookings or list_appointments. The description lacks context about typical use cases or when not to use it.

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

Deploy Server