Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

inventory_vendors_get

Read-onlyIdempotent

Retrieve a vendor record by its ServiceTitan ID to get exact details without pagination. Use inventory_vendors_list to search when the ID is unknown.

Instructions

Retrieve a vendor by its ServiceTitan ID. Returns the single upstream record without pagination; use inventory_vendors_list to search when the ID is unknown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesVendor ID
externalDataKeyNoExternal data key used with externalDataValues
externalDataValuesNoExternal data values used with externalDataKey
externalDataApplicationGuidNoExternal data application GUID for lookup

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

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds useful context beyond those annotations: it returns a single upstream record with no pagination. This gives the agent important expectations about the response shape and avoids any assumption that a list will be returned.

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 two sentences, front-loads the primary action, and wastes no words. It states the key behavior (single record, no pagination) and the alternative branch in the second sentence without unnecessary elaboration.

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 output schema is present, annotations comprehensively describe the operation's safety and idempotence, and the description covers the core invocation path and the correct fallback to inventory_vendors_list. Nothing essential for selecting or invoking this tool is missing.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description reinforces that 'id' is the ServiceTitan ID, matching the schema's 'Vendor ID,' but adds no additional semantic detail for the optional external data parameters. Baseline 3 is appropriate.

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 and resource: 'Retrieve a vendor by its ServiceTitan ID.' It also explicitly distinguishes itself from inventory_vendors_list by noting this returns a single record without pagination, so an agent can immediately recognize what this tool does and how it differs from its sibling.

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 gives explicit routing guidance: use inventory_vendors_list to search when the ID is unknown. This clearly implies the intended use case is when the ID is already known, and names the alternative tool directly.

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