ServiceTitan MCP

accounting_tax_zones_list

Read-onlyIdempotent

List and filter tax-zone definitions by ID, active status, or created/modified timestamps to resolve tax treatment identifiers.

Instructions

List one requested page of tax-zone definitions, filterable by IDs, active state, and created or modified timestamps. Use this catalog to resolve tax treatment identifiers; it does not return invoice transactions or calculated tax totals.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	No	Comma-delimited tax zone IDs
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, Name, CreatedOn
`active`	No	Filter by active status	True
`pageSize`	No	Records per page (default 50)
`includeTotal`	No	Include total count in response
`createdBefore`	No
`modifiedBefore`	No
`createdOnOrAfter`	No
`modifiedOnOrAfter`	No

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.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds meaningful behavioral context: results are paginated by page, the data is definitional/catalog-like, and invoice transactions and tax totals are outside its scope. No contradiction with annotations exists.

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 two sentences with no filler. The main action is front-loaded, filter capabilities are summarized in one clause, and the essential scope exclusion is stated at the end. Every sentence contributes value.

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

Completeness4/5

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

Given the output schema, annotations, and a 10-parameter input schema, the description provides adequate context: it states the resource type, pagination model, filter dimensions, and what the tool is not for. It could be slightly more complete by naming an alternative source for invoice transactions or tax totals, but nothing critical is missing for invoking the tool correctly.

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

Parameters4/5

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

Schema descriptions cover six parameters, but the four timestamp parameters lack descriptions, leaving 60% coverage. The description partially compensates by grouping them as 'created or modified timestamps' and clarifying they are filters. It does not describe every parameter, but the schema already handles the pagination and sorting details.

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 a specific verb and resource: 'List one requested page of tax-zone definitions.' It further clarifies the tool's role as a catalog for resolving tax treatment identifiers and explicitly distinguishes it from invoice transactions or calculated tax totals, making its purpose unmistakable.

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

Usage Guidelines4/5

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

The description gives a clear positive use case ('Use this catalog to resolve tax treatment identifiers') and an explicit negative boundary ('does not return invoice transactions or calculated tax totals'). It does not name a specific sibling tool for those alternatives, but the exclusions still guide selection well.

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

Deploy Server