Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

intel_membership_health

Read-onlyIdempotent

Summarize membership health for a date range using sales, cancellations, expirations, renewals, status movements, and conversion metrics.

Instructions

Summarize membership activity from Report 182 and business-unit membership opportunities and conversions from Report 178 for the selected date range. Returns active-at-end counts, sales, cancellations, expirations, renewals, other status movements, and conversion metrics; it does not calculate a cohort retention rate. includeServiceRevenue adds tenant-wide invoice service revenue for the period, which is not membership-attributed. Partial source failures are returned in _warnings.

Examples:

  • "How are memberships doing this year?" -> startDate="2026-01-01", endDate="2026-03-10"

  • "Show membership status movements last quarter" -> startDate="2025-10-01", endDate="2026-01-01"

  • "How many new signups vs cancellations?" -> startDate="2026-01-01", endDate="2026-03-10"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endDateYesEnd date (YYYY-MM-DD)
startDateYesStart date (YYYY-MM-DD)
includeServiceRevenueNoInclude tenant-wide totalServiceRevenue by fetching every available invoice page for the period. Default: false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • changedInput schema / properties / includeServiceRevenue / description
      Previous value: -"Include totalServiceRevenue from invoice pagination (adds ~1-2s latency). Default: false."New value: +"Include tenant-wide totalServiceRevenue by fetching every available invoice page for the period. Default: false."
  2. 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"
+}
  3. First observedv2.5.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, and the description adds substantial behavioral context beyond that: it identifies source reports, clarifies that includeServiceRevenue adds tenant-wide revenue not attributed to memberships, and discloses that partial source failures surface in _warnings. This gives an agent a realistic model of edge behavior.

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 appropriately sized and front-loaded: it opens with the core action and result set, adds caveats in the second sentence, and closes with three compact, useful examples. Every sentence contributes meaning without fluff.

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?

The tool has an output schema, so return-value details are already covered. The description supplies the remaining needed context: date-range semantics, required parameters, optional service-revenue behavior, exclusions, and partial-failure reporting. An agent has enough information to select and invoke this 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?

The schema already covers all parameters with descriptions, including the boolean semantics of includeServiceRevenue. The tool description adds value by mapping natural-language examples to startDate/endDate values and by clarifying that includeServiceRevenue is tenant-wide and not membership-attributed, which is not fully captured in the schema.

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 states a specific verb ('Summarize'), a clear resource ('membership activity from Report 182... and opportunities/conversions from Report 178'), and a date range scope. It lists the exact metrics returned and explicitly calls out what it does not calculate ('does not calculate a cohort retention rate'), which helps distinguish it from raw membership export or list tools.

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

Usage Guidelines3/5

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

The examples provide clear user-intent mappings to parameters ('How are memberships doing this year?' -> startDate='2026-01-01'...), which implies when the tool should be used. However, the description does not explicitly state when to use this tool over alternatives like export_memberships, memberships_status_changes_list, or other intel_* tools, so the guidance is implied rather than explicit.

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