ServiceTitan MCP

reporting_dynamic_value_sets_get

Read-onlyIdempotent

Resolve selectable values for a dynamic report parameter by supplying its dynamic set ID and paging inputs. Get the available choices from report metadata to populate dropdowns or validate selections.

Instructions

Resolve selectable values for a report dynamic-value-set identifier. Use values from the report definition to supply the required identifier and paging inputs when that report parameter offers dynamic choices.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (starts at 1)
`pageSize`	No	Records per page (default 50)
`dynamicSetId`	Yes	Dynamic set ID from report metadata
`includeTotal`	No	Include total count in response

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.0.0Sep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

First observedv2.5.1Apr 18, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds context about dynamic report parameters and report-definition dependencies, but no additional behavioral caveats such as auth needs or rate limits. No contradiction with annotations exists.

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 with no filler. The first sentence states the core purpose, and the second provides usage context. Every phrase contributes meaning and the key information is front-loaded.

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?

Given the rich annotations, complete parameter schema, and output schema, the description covers the essential invocation context: what the tool resolves and when/how to call it. Nothing critical is missing for an agent to select and invoke the 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?

Schema description coverage is 100%, so the baseline is 3. The description adds value by clarifying that dynamicSetId and paging inputs should be sourced from the report definition, which helps the agent know how to populate the parameters beyond their individual schema descriptions.

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: 'Resolve selectable values for a report dynamic-value-set identifier.' This clearly communicates that the tool retrieves option values for a dynamic report parameter, and no sibling tool covers the same operation, so it is readily distinguishable.

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 description explicitly says when to use the tool: 'when that report parameter offers dynamic choices.' It also tells the agent where to get inputs: 'Use values from the report definition.' It does not name alternatives or exclusions, but there is no closely overlapping sibling tool, so the guidance is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server