Sales MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LANGGRAPH_URL | Yes | URL of the LangGraph server | |
| OPENAI_API_KEY | No | OpenAI API key (optional if using Ollama) | |
| LANGGRAPH_ASSISTANT_ID | Yes | Assistant ID for the skills agent |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_agentA | Ask the LangGraph skills agent a natural-language question and render its response as a Prefab dashboard card. Call this tool whenever the user asks a question that matches any of the loaded skills below — even when the user does not explicitly say "use the skills agent". Do not answer from memory or invent data; route the question through this tool so the agent can query the live database, detect anomalies, and pause for human review when needed. Loaded skills:
Pass an optional |
| resume_reviewB | Resume a paused thread with the human's decision. Returns a Prefab component tree (NOT a PrefabApp) so the dashboard's
|
| check_review_statusB | Return Called from the dashboard's |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Prefab Renderer (ask_agent) |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: ask_agent for querying the agent, resume_review for resuming paused threads, and check_review_status for querying thread state. No overlap.
All tool names follow a consistent verb_noun pattern with underscores (ask_agent, resume_review, check_review_status), making them predictable and clear.
Three tools is well-suited for a focused agent interface server. Each tool covers a core interaction step (ask, resume, check status) without unnecessary extras.
The tool set provides full lifecycle support for the sales analytics agent: asking questions, handling human reviews, and checking status. No obvious gaps for the intended use case.