Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

dispatch_projects_notes_list

Read-onlyIdempotent

Retrieve paginated notes for a project by providing its project ID. Includes page size and total count options for reviewing project communication.

Instructions

List one page of notes attached to a known project. Requires the project ID; use dispatch_projects_get for the project record itself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProject ID
pageNoPage number (starts at 1)
pageSizeNoRecords per page (default 50)
includeTotalNoInclude total count in response

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

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

Annotations already cover read-only, non-destructive, idempotent behavior, so the description's 'one page' qualifier and 'known project' precondition add modest extra context. It does not disclose return ordering, error behavior, or pagination defaults, but with strong annotations and an output schema, nothing here contradicts or misleads.

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 short sentences carry purpose, prerequisite, and the key sibling distinction without any filler. The most important fact (what the tool lists) 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?

For a simple paginated read tool with a required ID, a complete input schema, rich annotations, and an output schema, this description covers the necessary context. It tells the agent what is returned, what must be supplied, and where to go for the parent record.

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 baseline applies. The description adds only that the project ID is required and that the result is a single page; it does not add detail about page, pageSize, or includeTotal beyond what the schema already documents.

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 names a specific verb ('List'), a specific resource ('notes attached to a known project'), and a pagination qualifier ('one page'). It also distinguishes itself from dispatch_projects_get by clarifying that the get tool returns the project record itself, which removes the most likely ambiguity.

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?

It states the prerequisite ('Requires the project ID') and explicitly names the alternative for when the project record itself is wanted ('use dispatch_projects_get'). This gives the agent a clear branch: use this tool for notes when the project ID is already known, and use the get tool for the record.

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