ServiceTitan MCP

dispatch_installed_equipment_attachments_get

Read-onlyIdempotent

Retrieve a stored attachment for installed equipment by supplying its ServiceTitan storage path. Returns the client-decoded attachment response.

Instructions

Request an installed-equipment attachment by its ServiceTitan storage path. Returns the client-decoded attachment response; the pinned API does not define a response-body schema. Supply the exact known path; use dispatch_installed_equipment_get for the equipment record itself.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	No	Storage path for a previously-uploaded attachment

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 indicate a safe read-only, idempotent operation. The description adds useful behavioral context: the response is client-decoded, and the pinned API defines no response-body schema. This sets appropriate expectations without relying solely on structured hints.

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 three focused sentences with no fluff. It front-loads the core purpose, then explains the response behavior and the relevant sibling alternative. Every sentence contributes necessary guidance.

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 single parameter, rich annotations, an output schema, and a clear sibling distinction, the description is nearly complete. It could be slightly more explicit about error behavior for invalid paths, but nothing critical 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 single parameter 'path' is already fully described in the schema as 'Storage path for a previously-uploaded attachment.' The description reinforces that the path must be exact, which is useful, but the schema carries most of the parameter meaning.

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 clearly states the tool requests an installed-equipment attachment using a ServiceTitan storage path. It distinguishes itself from the related sibling dispatch_installed_equipment_get, so an agent can immediately tell what resource this tool operates on.

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 explicitly instructs the agent to supply the exact known path and points to dispatch_installed_equipment_get as the correct tool when the equipment record itself is needed. This gives clear routing guidance and prevents misuse.

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

Deploy Server