Sun 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sun_summarizeC | Summarize current session and save as .mdc file when -sun command is used. Use -sun for Chinese or -sun en for English |
| sun_list_summariesB | List all saved session summaries |
| sun_get_summaryC | Get content of a specific summary file |
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 has a clearly distinct purpose: sun_get_summary retrieves content of a specific file, sun_list_summaries lists all available summaries, and sun_summarize creates and saves a new summary. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tools follow a consistent 'sun_verb_noun' pattern with snake_case, using descriptive verbs like 'get', 'list', and 'summarize'. This uniformity makes the tool set predictable and easy to understand.
With 3 tools, the server is well-scoped for session summary management, covering creation, listing, and retrieval. Each tool earns its place without being overly sparse or bloated, fitting typical use cases efficiently.
The tools provide good coverage for the session summary domain, including create (summarize), read (get_summary), and list operations. A minor gap exists in update or delete functionality, but agents can likely work around this for basic workflows.