Skip to main content
Glama
Sign In
ServiceTitan MCP Server

ServiceTitan MCP Server

by Voryn-Software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_employees

Retrieve a list of employees, with the option to filter for active employees only.

Instructions

List employees. Optionally filter to active only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_employees"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
page_sizeNo
active_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations exist, so the description carries full burden. It mentions filtering but does not disclose default behaviors (e.g., active_only defaults to true) or any side effects. Pagination behavior and possible limits are omitted, making the tool's operation less transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise at two short sentences with no superfluous content. However, it could be slightly improved by incorporating parameter meanings without adding length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (list with pagination and boolean filter) and the presence of an output schema, the description covers the core purpose but leaves gaps in parameter explanation and default behavior. It is minimally viable but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, requiring the description to explain parameters. It only addresses the active_only parameter implicitly ('filter to active only') but provides no information about page or page_size, which are critical for usage. This is insufficient for an agent to invoke the tool correctly without additional inference.

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 clearly states 'List employees' which identifies the verb and resource. It also mentions optional filtering, which adds some specificity. However, it does not differentiate from the many sibling list tools (e.g., list_customers) beyond the resource name, nor does it indicate pagination behavior.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like get_employee (single employee) or other list tools. There is no mention of prerequisites or when-not to use it, leaving the agent to infer usage from context alone.

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