Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

intel_csr_performance

Read-onlyIdempotent

Summarize customer service representative performance for a selected date range, showing booked jobs, revenue, average ticket, and rankings. Filter by business unit to compare CSR results.

Instructions

Summarize CSR-attributed jobs from Report 162 for the selected date range. Returns booked-job counts, revenue, average ticket, campaign and job-type mixes, rankings, and team averages; an optional business-unit name narrows matching report rows. Report execution is cached briefly and may wait for per-report/client spacing; unavailable source data is identified in _warnings.

Examples:

  • "How are our CSRs performing this month?" -> startDate="2026-03-01", endDate="2026-04-01"

  • "Show CSR booking revenue for last quarter" -> startDate="2025-10-01", endDate="2026-01-01"

  • "Which CSR is booking the most revenue for plumbing?" -> startDate="2026-01-01", endDate="2026-03-10", businessUnitName="Plumbing"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endDateYesEnd date (YYYY-MM-DD)
startDateYesStart date (YYYY-MM-DD)
businessUnitIdNoFilter by business unit ID
businessUnitNameNoFilter by business unit name (resolved via cache, e.g. 'HVAC'). Alternative to businessUnitId.

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

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds valuable behavioral context beyond that: report execution is cached briefly, may wait due to per-report/client spacing, and unavailable source data is surfaced in _warnings. This gives the agent realistic expectations about latency and error reporting.

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 well-structured: a front-loaded purpose and metric list, one sentence on execution behavior, then three directly relevant examples. Every sentence contributes useful information, with no filler or repetition.

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?

With an output schema present, the description does not need to document return fields. It covers the source report, the date-window requirement, optional business-unit filtering, caching and spacing delays, and warning behavior, which is complete for both selection and invocation. The annotations handle the safety profile.

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 description coverage is 100%, so the baseline is 3. The examples add real meaning above the schema by showing that endDate is exclusive, as this month maps to 2026-03-01 through 2026-04-01, and last quarter maps to 2025-10-01 through 2026-01-01. This clarifies date-range semantics that the schema alone does not state.

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 leads with a specific verb and resource: Summarize CSR-attributed jobs from Report 162. It then enumerates the exact metrics returned, such as booked-job counts, revenue, average ticket, mixes, rankings, and team averages, making its purpose unmistakable and distinguishable from the many intel_* siblings.

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?

The natural-language examples provide clear trigger scenarios, such as asking about CSR performance for a month, quarter, or specific business unit. It does not explicitly name sibling alternatives or state when not to use this tool, but the CSR-attributed scope and examples give sufficient context for when it applies.

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