Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

crm_customers_get

Read-onlyIdempotent

Retrieve a single customer record by ID from ServiceTitan, returning the complete customer data associated with that ID.

Instructions

Retrieve one customer record by ID, including the customer data returned by ServiceTitan. Use crm_customers_list to search by name, address, phone, external data, activity, or date ranges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCustomer ID

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. Addedv2.6.2
  3. Removedv2.6.2
  4. 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 declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description only needs to add extra context. The phrase 'including the customer data returned by ServiceTitan' informs the agent that the response contains the raw ServiceTitan customer payload, which is useful behavioral context beyond the annotations. It does not specify not-found behavior, but the simplicity of the tool and presence of an output schema reduce that gap.

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 tightly written sentences accomplish everything: the first states the exact purpose and scope, the second directs to the correct sibling for broader searches. There is no repetition or filler, and the key information is front-loaded.

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 read tool with full annotation coverage and an output schema, the description is complete. It explains the tool's scope, points to the alternative for search scenarios, and relies on structured metadata for safety and return-type information. An agent has enough information to invoke this tool correctly without further clarification.

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 input schema fully documents the single 'id' parameter with 100% coverage, so the description need not repeat parameter details. The phrase 'by ID' adds no new semantic information beyond the schema. A baseline score of 3 is appropriate when the schema carries the parameter documentation burden.

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 ('Retrieve') and resource ('one customer record by ID'), clearly stating what the tool does. It also implicitly differentiates from crm_customers_list, which is framed as the search-by-attributes alternative, making the tool's unique role clear.

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 directs the agent to crm_customers_list for searching by name, address, phone, external data, activity, or date ranges, establishing exactly when to use the alternative. It implies that crm_customers_get is for direct ID-based lookup, providing clear selection criteria.

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