Pinpoint dealership sales tools

Follow-up cadence for a situation

follow_up_cadence

Read-only

The follow-up sequence for a sales situation (new web lead, missed inbound call, unconfirmed appointment, no-show, quote without an appointment, pricing question without a meeting, text thread gone quiet, new customer first week): the starting event and each step's timing, channel, purpose, message with the names filled in, and the reply that stops it. Use startLabel to anchor the sequence; a step's whenLabel takes precedence over its retained legacy day value.

Input Schema

TableJSON Schema

Name	Required	Description
`rep`	No	The rep's first name
`company`	No	Your company name
`product`	No	What the customer asked about, for example "umbrella policy"
`situation`	Yes	The situation slug
`day_and_time`	No	The day and time on the table, for example "Saturday at 12:30"
`customer_first_name`	No	The customer's first name

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 25, 2026

addedInput schema / properties / company

Added value: +{
+  "description": "Your company name",
+  "type": "string"
+}

removedInput schema / properties / dealership

Removed value: -{
-  "description": "The dealership name",
-  "type": "string"
-}

addedInput schema / properties / product

Added value: +{
+  "description": "What the customer asked about, for example \"umbrella policy\"",
+  "type": "string"
+}

changedInput schema / properties / rep / description

Previous value: -"The salesperson's first name"New value: +"The rep's first name"

changedInput schema / properties / situation / enum

Previous value: -[
-  "new-internet-lead",
-  "missed-inbound-call",
-  "appointment-unconfirmed",
-  "no-show",
-  "quote-without-appointment",
-  "trade-question-without-appointment",
-  "text-thread-gone-quiet",
-  "sold-first-week"
-]New value: +[
+  "new-internet-lead",
+  "missed-inbound-call",
+  "appointment-unconfirmed",
+  "no-show",
+  "quote-without-appointment",
+  "pricing-question-without-meeting",
+  "text-thread-gone-quiet",
+  "new-customer-first-week"
+]

removedInput schema / properties / vehicle

Removed value: -{
-  "description": "The vehicle of interest",
-  "type": "string"
-}

First observedSep 22, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The annotations declare readOnlyHint=true and openWorldHint=false, so the description builds on that by detailing what the response contains and the precedence rule for whenLabel over legacy day values. It also notes that names are filled in, which clarifies the effect of the rep/company/customer parameters. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with an embedded list, efficiently conveying the tool's purpose and output. It is not overly verbose, though it could be split for readability. The key information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given there is no output schema, the description carries the burden of explaining the response, which it does by listing the components (timing, channel, purpose, message, reply). It explains the anchoring behavior and precedence. However, it does not mention how optional parameters are handled when omitted, nor the exact response structure (e.g., JSON format). Overall, it is adequate for a read-only tool.

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?

All parameters are described in the schema (100% coverage), so the description adds little beyond the schema. It references startLabel and whenLabel which are not parameters, but that clarifies behavior rather than parameter semantics. The description does not elaborate on the meaning of situation or day_and_time beyond the schema.

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 tool returns a follow-up sequence for a sales situation, enumerates the eight situations it covers, and specifies the content of the sequence (timing, channel, purpose, message, reply). This distinguishes it from related tools like write_follow_up_texts by focusing on the cadence rather than individual texts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus siblings such as write_follow_up_texts, check_follow_up_text, or tailor_follow_up_cadence. It only explains how to anchor the sequence, not when to choose it. An agent would have to infer usage from the name and schema.

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

All Pinpoint dealership sales tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?