INDIVIDUAL MCP TOOL
score_crm_note
Scores a CRM note written after a sales call or text thread against what a complete note carries, and rewrites it complete with brackets for missing facts.
LIVE ENDPOINT
https://usepinpoint.ai/api/mcp/sales-tools
Connect to this endpoint to inspect the live schema for score_crm_note and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.pinpoint-sales-tools]
url = "https://usepinpoint.ai/api/mcp/sales-tools"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"pinpoint-sales-tools": {
"type": "http",
"url": "https://usepinpoint.ai/api/mcp/sales-tools"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: pinpoint-sales-tools
Remote MCP URL: https://usepinpoint.ai/api/mcp/sales-tools
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"pinpoint-sales-tools": {
"url": "https://usepinpoint.ai/api/mcp/sales-tools"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"pinpoint-sales-tools": {
"type": "http",
"url": "https://usepinpoint.ai/api/mcp/sales-tools"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "pinpoint-sales-tools",
"transport": "streamable-http",
"url": "https://usepinpoint.ai/api/mcp/sales-tools"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
check_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.check_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.call_recording_consent— 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.ai_caller_disclosure— 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.follow_up_cadence— 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.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.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.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.