Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

intel_estimate_pipeline

Read-onlyIdempotent

Analyze ServiceTitan estimates by open, sold, and dismissed pipeline with conversion, close speed, and age; flag estimates older than 30 days. Filter by date or salesperson to assess performance.

Instructions

Analyze all fetched estimate pages as an open, sold, and dismissed pipeline, with value, conversion, close speed, age buckets, and open estimates older than 30 days. startDate and endDate bound estimate creation timestamps; when both are supplied, Report 172 adds technician sales metrics. soldById filters both sources. Partial source failures are returned in _warnings.

Examples:

  • "What's our close rate on estimates?" -> startDate="2026-01-01", endDate="2026-03-10"

  • "Show me stale estimates over 30 days" -> returns staleEstimates automatically

  • "How is Andrew doing on sales?" -> soldById=<Andrew's ID>

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endDateNoFilter estimates created before this date
soldByIdNoFilter by salesperson/technician
startDateNoFilter estimates created after this date

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.1/5.0
Behavior4/5

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

Adds valuable runtime behavior beyond annotations: partial source failures are surfaced in _warnings, soldById filters both sources, and providing both dates triggers technician sales metrics. It also notes automatic stale-estimate handling. No contradiction with the readOnly/idempotent annotations.

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 compact and front-loaded: purpose first, then parameter behavior, then three illustrative examples. Every sentence adds value without repeating the schema or annotations.

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?

With an output schema present and annotations covering the safety profile, the description sufficiently covers what the tool does, how parameters interact, and how partial failures are flagged. Minor ambiguity around 'all fetched estimate pages' and lack of explicit sibling routing are the only notable gaps.

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 coverage is 100%, but the description enriches parameter meaning: startDate/endDate are creation-timestamp bounds, both dates together enable Report 172 metrics, and soldById applies across both sources. Examples also demonstrate concrete parameter usage.

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 states a specific analytical verb ('Analyze') and a concrete resource (estimate pages) with clear dimensions: open, sold, and dismissed pipeline, value, conversion, close speed, age buckets, and stale estimates. It is distinguishable from raw estimate list/export tools, though it does not explicitly name a sibling alternative.

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?

Provides natural-language examples that map user intents to parameter values, and clearly explains conditional behavior (Report 172 only when both dates are supplied). It implies when to use this tool, but does not explicitly contrast it with alternatives like estimates_list or other intel tools.

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