serve7-mcp-connectors
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| customer_lookupA | Look up a customer record by customer ID, email, or phone number. Returns account status and tier so an agent (human or AI) can personalize the interaction. Call this first in nearly every flow. |
| create_support_ticketA | File a new support ticket for a customer when their issue can't be resolved in the current interaction. Use retrieve_status afterward to check progress on a ticket already created. |
| retrieve_statusA | Check the current status of a previously created support ticket by its ticket ID. Use this before telling a customer their issue is still 'in progress' vs resolved. |
| schedule_appointmentB | Book an appointment (call-back, in-branch visit, technician visit, etc.) for an existing customer. |
| update_crm_recordA | Patch fields on an existing customer's CRM record (e.g. after verifying a new phone number or email during a call). Only include the fields you want changed. |
| retrieve_knowledgeA | Search the knowledge base for articles relevant to a customer's question. Returns the top matches with a relevance score and source URL so responses can be grounded and cited. |
| create_taskA | Create a follow-up task for a human teammate — e.g. 'call customer back with a refund confirmation' — when something needs manual handling after the AI-driven part of the interaction ends. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a clearly distinct resource and action: customer lookup, ticket creation/status, appointment scheduling, CRM patching, knowledge search, and task creation. There is no meaningful overlap or ambiguity between tool purposes.
Most tools follow the verb_noun pattern (create_support_ticket, retrieve_status, schedule_appointment, update_crm_record, retrieve_knowledge, create_task). The exception is customer_lookup, which reverses the order to noun_verb, creating a minor consistency deviation.
Seven tools is a well-scoped size for a customer support/CRM connector. Each tool covers a distinct workflow step, and none feel redundant or unnecessary.
The surface covers customer lookup, ticket creation and status, knowledge retrieval, and follow-up tasks, but ticket lifecycle is incomplete (no update or close) and appointment management lacks cancellation/rescheduling. These are notable gaps for a full customer support workflow.