SuzyQ MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_suzyqB | Send a message to SuzyQ chatbot and get a response. SuzyQ is your research co-pilot that can help you with questions about surveys, missions, actions, data analysis, and more within the Suzy platform. |
| new_suzyq_conversationA | Start a new conversation with SuzyQ. This will clear the current conversation history and start fresh. |
| get_suzyq_conversation_historyB | Get the conversation history for a specific conversation with SuzyQ. |
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 3 tools
Each tool serves a distinct, non-overlapping function: sending a message, starting a fresh conversation, and retrieving history. There is no ambiguity about which tool to invoke for a given action.
All tool names follow a clear verb_suzyq_noun snake_case pattern: ask_suzyq, new_suzyq_conversation, get_suzyq_conversation_history. Naming is predictable and easy to learn.
Three tools is an appropriate, minimal set for the server's stated purpose of interacting with a SuzyQ chatbot session. Each tool is meaningful and there is no bloat or obviously missing core function.
The core lifecycle of a chatbot session is covered: start, ask, and retrieve history. Minor gaps like explicitly deleting a conversation or listing past conversations exist, but they are not essential to the primary workflow.