Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

dispatch_jobs_cancel_reasons_list

Read-onlyIdempotent

Fetch job cancellation reason details for a list of specific IDs. Pass up to 50 comma-separated cancel reason IDs to return matching records.

Instructions

Look up job cancellation reasons for a supplied list of known IDs. This non-paginated Jobs endpoint is distinct from dispatch_job_cancel_reasons_list, which browses and filters the reason catalog.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoComma-separated cancel reason IDs (maximum 50)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}
  2. First observedv2.5.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safe read-only, idempotent, non-destructive profile. The description adds the meaningful behavioral trait that this endpoint is non-paginated, which is useful context for an agent deciding how to handle results. This goes beyond what the annotations alone communicate.

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 compact sentences front-load the core purpose, then immediately add the distinguishing non-pagination and sibling-tool information. Every sentence earns its place with no filler or redundancy.

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?

For a single-parameter, output-schema-backed lookup tool with comprehensive annotations, the description is complete. It explains the lookup scope, the non-paginated behavior, and the difference from the nearest sibling, leaving no critical information 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 the schema already documents that 'ids' is a comma-separated list of cancel reason IDs with a maximum of 50. The description's phrase 'known IDs' reinforces the lookup semantics but adds no new parameter details beyond the schema.

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 uses a specific verb ('look up'), a clear resource ('job cancellation reasons'), and a clear input mode ('for a supplied list of known IDs'). It also explicitly distinguishes itself from the similarly named sibling dispatch_job_cancel_reasons_list, so an agent can reliably tell the two apart.

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?

The description provides explicit usage context: use this endpoint to look up known cancellation reason IDs. It also names the alternative catalog-browsing endpoint and contrasts it ('browses and filters the reason catalog'), effectively telling the agent when not to use this tool.

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