Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pricebook_materials_markup_get

Read-onlyIdempotent

Get a material markup range by its ServiceTitan ID to view exact pricing details without searching.

Instructions

Retrieve a material markup range by its ServiceTitan ID. Returns the single upstream record without pagination; use pricebook_materials_markup_list to search when the ID is unknown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMaterial markup 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. First observedv2.5.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare the operation read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond annotations: it returns a single upstream record and does not paginate. This is helpful and not redundant.

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 sentences with no filler. The core retrieval action is front-loaded, the no-pagination behavior is stated, and the alternative is provided in the same sentence as the search condition.

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?

This is a simple one-parameter get-by-ID tool with an output schema and safety annotations. The description covers the key behavior (single record, no pagination) and directs the agent to the list tool when an ID is unavailable. Nothing essential is missing.

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 fully documents the single required id parameter, so the baseline is 3. The description adds a small but useful semantic upgrade by calling it a 'ServiceTitan ID', clarifying that the ID refers to the upstream ServiceTitan entity.

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 clearly states the verb 'Retrieve', the resource ('material markup range'), and the lookup key ('by its ServiceTitan ID'). It also distinguishes this from the list tool by emphasizing 'single upstream record', so an agent can tell which tool to use.

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 routes to the sibling tool: 'use pricebook_materials_markup_list to search when the ID is unknown'. This is clear when-to-use and when-not-to-use guidance.

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