ServiceTitan MCP

pricebook_equipment_get

Read-onlyIdempotent

Retrieves an equipment item's details from ServiceTitan by its unique ID. Use when the ID is known; if unknown, search using the list endpoint.

Instructions

Retrieve equipment item by its ServiceTitan ID. Returns the single upstream record without pagination; use pricebook_equipment_list to search when the ID is unknown.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Equipment ID
`externalDataApplicationGuid`	No	External data application GUID

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 mark the tool read-only, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds behavioral detail by promising a single upstream record with no pagination, which helps the agent understand the return shape beyond the annotations. It does not discuss error behavior, but that is a minor omission given the strong annotation coverage.

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 the full message: action, return-shape guarantee, and routing to the sibling when the ID is unknown. There is no filler or repetition of the schema. The front-loaded verb helps an agent scan quickly.

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 simple get-by-ID tool, the description covers what the agent needs: what it returns (single record, no pagination) and when to use this instead of the list. The output schema provides the return structure, and the annotations cover safety and idempotence. Nothing important is missing for correct invocation.

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?

The schema documents both parameters with descriptions, and schema description coverage is 100%, so the baseline is 3. The description adds a small amount of semantic value by clarifying that 'id' is the ServiceTitan ID, which is more specific than 'Equipment ID'. It does not add meaning for externalDataApplicationGuid, but the schema already covers it.

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 ('Retrieve'), resource ('equipment item'), and key identifier ('ServiceTitan ID'). It also distinguishes itself from the list sibling by specifying that it returns a single, non-paginated upstream record. This leaves no ambiguity about what the tool does.

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?

Explicitly says when to use this tool (when the ServiceTitan ID is known) and names the alternative (pricebook_equipment_list) for when the ID is unknown. This gives the agent a clear decision rule for choosing between the get and list variants. No other guidance is needed for such a straightforward lookup.

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

Deploy Server