ai-business-system-advisor-mcp

by tenkai2018

Overview Schema Source Related Servers Discussions Admin

Map Customer Touchpoints

map_customer_touchpoints

Read-onlyIdempotent

Map customer touchpoints to identify trust-sensitive moments, automation-safe areas, and gaps in the customer journey for AI workflow planning.

Instructions

Maps customer-facing workflow stages, trust-sensitive moments, automation-safe areas, human-critical areas, missing information, and confidence.

Input Schema

TableJSON Schema

Name	Required	Description
`aiIdea`	No	AI or automation idea that may affect customer touchpoints.
`touchpoints`	No	Specific customer-facing moments, handoffs, or interactions to review.
`businessType`	No	Type of business being reviewed.
`riskConcerns`	No	Concerns about trust, customer experience, brand reputation, privacy, or quality control.
`salesProcess`	No	How leads are qualified, sold, and converted before delivery begins.
`currentProblem`	No	Main customer journey or workflow problem the user wants to solve.
`supportProcess`	No	How customer questions, issues, tickets, or requests are handled.
`currentWorkflow`	No	Current workflow steps, tools, owners, and handoffs.
`customerJourney`	No	Known customer journey stages from first contact through retention.
`deliveryProcess`	No	How the business delivers the offer or service after onboarding.
`recoveryProcess`	No	How complaints, refunds, exceptions, or service recovery are handled.
`retentionProcess`	No	How renewals, repeat purchases, referrals, or ongoing customer value are managed.
`onboardingProcess`	No	How new customers are welcomed, scoped, educated, or set up.

Output Schema

TableJSON Schema

Name	Required	Description
`confidence`	Yes	Confidence level based on the clarity and completeness of the provided business context.
`touchpoints`	Yes	Reviewed customer touchpoints with classification, reason, and suggested control.
`humanCriticalAreas`	Yes	Areas where human review or ownership should remain explicit.
`missingInformation`	Yes	Information the user should provide to improve diagnostic confidence.
`automationSafeAreas`	Yes	Areas that appear suitable for AI assistance or automation with low risk.
`trustSensitiveMoments`	Yes	Moments where customer trust, expectations, or brand perception may be at risk.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.10Jul 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds no further behavioral context, such as what happens with partial inputs or whether all parameters are required. Minimal additional value beyond annotations.

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, very concise with no wasted words. It is front-loaded but could benefit from bullet points for better readability. Still, it is efficient.

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

Completeness2/5

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

Given the complexity (13 parameters, many siblings, output schema exists), the description is too sparse. It lacks guidance on parameter importance, prerequisites, or how the output is structured. Not complete enough for effective selection.

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 baseline is 3. The description does not elaborate on parameter semantics or relationships beyond the schema, adding no extra meaning.

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 clearly states the tool maps customer-facing workflow stages and related aspects, using a specific verb ('Maps') and resource. However, it does not differentiate from siblings like 'assess_trust_control_risks', which may overlap.

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 alternatives. No context, prerequisites, or exclusion criteria are given, leaving the agent to guess the appropriate scenario.

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

Deploy Server