Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

st_result_read

Read-onlyIdempotent

Retrieve a large JSON result in bounded chunks by starting at offset 0 and following nextOffset to reconstruct the full response. Access oversized tool outputs stored for five minutes in the current session.

Instructions

Retrieve a stored large result as bounded JSON text chunks. Start at offset 0, concatenate text in nextOffset order, then parse JSON. Results expire after five minutes and belong to this session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoZero-based character offset for the next JSON text chunk; start at 0 and then use nextOffset
resultIdYesSession-owned result identifier returned by a tool whose response exceeded the inline limit

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.1
    • addedInput schema / properties / offset / description
      Added value: +"Zero-based character offset for the next JSON text chunk; start at 0 and then use nextOffset"
    • addedInput schema / properties / resultId / description
      Added value: +"Session-owned result identifier returned by a tool whose response exceeded the inline limit"
  2. Addedv3.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it reveals important stateful behavior: results expire after five minutes, belong to this session, and chunks must be concatenated in nextOffset order before parsing. This goes beyond the annotation defaults and is critical for correct use.

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 front-load the purpose and then deliver the required chunk-reading protocol without wasted words. Every sentence carries necessary operational information.

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?

For a two-parameter tool with a rich schema, an output schema, and read-only/idempotent annotations, the description fully covers the retrieval workflow and the session/expiry constraints. Nothing essential is missing for an agent to invoke it 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?

The schema already documents both parameters at 100% coverage. The description adds cross-parameter protocol meaning by tying offset to the nextOffset sequence and by defining the result as JSON text chunks, which helps an agent understand how resultId and offset work together.

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 uses a specific verb and resource ('Retrieve a stored large result') and clarifies that the result is delivered as bounded JSON text chunks. It is clear and not tautological, though it does not explicitly compare with or distinguish itself from any sibling tool.

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?

It gives concrete usage steps: start at offset 0, concatenate in nextOffset order, then parse JSON, with a five-minute expiry and session scoping. It does not name alternatives or explicit when-not-to-use conditions, but the instructions are explicit enough for the tool's narrow purpose.

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