Resources

Use the tools from your own agent.

Add these sales tools to an AI assistant through MCP, or use them in code through the JSON API. No key or signup. Credit Pinpoint and link the source page with each result.

MCP server URL for your assistant

https://usepinpoint.ai/api/mcp/sales-tools

Add to your assistant

Add this server as a connector. It is stateless Streamable HTTP over JSON-RPC, read-only, with 10 data tools always and 8 assistant tools when the model provider is on.

  • Claude. Settings, Connectors, Add custom connector, paste the URL. No authentication.
  • ChatGPT. Settings, Connectors, Advanced, Developer mode, Create, paste the URL as an MCP server.
  • Cursor, Windsurf, Claude Code and others. Add to the MCP configuration:
{
  "mcpServers": {
    "pinpoint": {
      "url": "https://usepinpoint.ai/api/mcp/sales-tools"
    }
  }
}
API reference and limits

Call the JSON API

GET one URL per tool. Results are JSON with a source block naming Pinpoint and the page to link. The list of tools with their parameters is at /api/tools/list and described in OpenAPI.

  • Check an appointment ask

    Deterministic check of one appointment ask on a sales call using six fixed text-pattern rules: day, clock time, holding the time, confirmation question, naming what the customer asked about or promising it ready, and follow-up. Returns a structured score, per-part flags and fixes, and a fixed template example that reuses a detected day and time or supplies sample values when absent. Runs without an AI model. Use this for repeatable rule-based scoring; use review_appointment_ask for contextual AI feedback and a tailored rewrite.

    https://usepinpoint.ai/api/tools/check_appointment_ask?text=Let%20me%20hold%20Saturday%20at%2012%3A30%20for%20you
  • Check a follow-up text

    Checks a sales follow-up text message against eight practices: identifies the sender and company, refers to what the customer asked about, one question at most, a specific next step, no price or payment or discount, an easy way out, two segments or fewer, no all-caps urgency. Returns what passed, what failed and why.

    https://usepinpoint.ai/api/tools/check_follow_up_text?text=Let%20me%20hold%20Saturday%20at%2012%3A30%20for%20you
  • Call recording consent by state

    Whether one party or every party must consent before a phone call is recorded in a US state, the statute, a note for sales teams, and the greeting, outbound and text notices to use on your calls. All 50 states and DC. General information, not legal advice.

    https://usepinpoint.ai/api/tools/call_recording_consent?state=FL
  • AI caller disclosure by state

    What a US state requires when an automated or AI voice assistant answers a sales team's missed calls or places an approved outbound call: the AI disclosure rule, the consent rule for automated calls, the statute, the federal baseline, and what the assistant should say. All 50 states and DC. General information, not legal advice.

    https://usepinpoint.ai/api/tools/ai_caller_disclosure?state=FL
  • Follow-up cadence for a situation

    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.

    https://usepinpoint.ai/api/tools/follow_up_cadence?situation=new-internet-lead
  • Sales roleplay card

    A practice card for a sales roleplay: a customer type (twelve, from the price shopper to the callback who went quiet) and an objection (eight, from "I need to think about it" to "just email me the numbers"): the customer's opening line, what they want and fear, their tells, the objection as the customer says it, the rep's goal, what a strong answer sounds like, and the feedback checklist.

    https://usepinpoint.ai/api/tools/roleplay_card?customer_type=price-shopper&objection=need-to-think-about-it
  • CRM note checklist

    What a complete CRM note carries after a sales call or text thread, in five sections, with an example of a strong note and the lead statuses that mislead managers.

    https://usepinpoint.ai/api/tools/crm_note_checklist
  • Sales call scorecard

    The eighteen-item pass-or-fail scorecard for a sales call, in five groups (open, discovery, the ask, control, close and record), with the scoring rules and the four-minute review method.

    https://usepinpoint.ai/api/tools/call_scorecard
  • Conversation signals library

    The 40 moments in a sale worth acting on, in six groups (buying signals, appointment handling, follow-up gaps, coaching moments, record gaps, agent handoffs). Without a signal, returns the list; with a signal slug, returns what it sounds like, why it matters, what to do next, how to coach it and how to practice it.

    https://usepinpoint.ai/api/tools/conversation_signals
  • Sales conversation glossary

    Plain definitions of the 92 terms in the Pinpoint sales conversation glossary, from appointment set rate to speed to lead and quiet hours. Accepts a term's other names too. Returns the matching term, or the closest matches.

    https://usepinpoint.ai/api/tools/sales_glossary?term=appointment%20set%20rate

Use the assistant API

POST to /api/ask with { "tool": "composer", "input": "what happened", "context": "names and settings" } for the same replies the tool pages give: ask-checker, composer, text-check, crm-note, cadence, scorecard, notice, disclosure, and the practice call as roleplay and roleplay-feedback with a messages array. The reply is { "text": "...", "source": { ... } }. Through MCP the same tools are named review_appointment_ask, write_follow_up_texts, rewrite_follow_up_text, score_crm_note, score_call, tailor_follow_up_cadence, answer_recording_question and answer_ai_caller_question.

Attribution and limits

  • Credit. Say the result comes from Pinpoint (usepinpoint.ai) and link the page in source.url. The consent and disclosure datasets are CC BY 4.0.
  • Downloads. The two state datasets are files too, with one row for each of the 50 states and DC under CC BY 4.0: Telephone call recording consent rules by US state as CSV or JSON, and AI and automated caller disclosure rules by US state as CSV or JSON. Each CSV opens with four lines that start with # (the name, the credit, the license and the review date), which pandas skips with skiprows=4.
  • Nothing stored. Requests are answered and forgotten; do not send customer names or numbers.
  • Limits. Data tools are cached for an hour and not limited. Assistant tools allow twenty requests per address every ten minutes and inputs up to 2,400 characters (6,000 for a transcript).
  • General information. The state datasets and anything the assistant says about recording, disclosure or consent are general information, not legal advice.
  • Synthetic examples. Names and conversations in examples are synthetic.
  • Earlier names. Parameter names and values from earlier versions of these tools still work. dealership_glossary answers as sales_glossary, and the state results repeat note as dealership_note through January 12, 2027. The earlier MCP address, /api/mcp, keeps working: through the same date it keeps its earlier server name and tool names, then it answers as pinpoint-sales-tools. Responses at an earlier name or address carry a Deprecation header and a Link to the new one.

Back to resources