Semesters 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 |
|---|---|
| generate_dyslexia_uiB | Generate dyslexia-friendly UI components |
| review_trauma_contentB | Review content for trauma-informed language |
| validate_og_activityB | Validate activity against Orton-Gillingham principles |
| generate_phoneme_activityC | Generate multisensory phoneme practice activity |
| review_code_safetyC | Review code for trauma-informed principles |
| generate_stress_protocolB | Generate stress detection and response protocol |
| generate_engagement_activityC | Generate intrinsically motivating learning activity |
| validate_engagement_safetyC | Check if engagement mechanic might cause trauma or pressure |
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 8 tools
Most tools have distinct targets (UI vs activity vs protocol), but review_trauma_content and validate_engagement_safety both address trauma-related concerns, which could cause some confusion. The descriptions likely clarify the difference, but the boundaries are slightly fuzzy.
All tool names follow a consistent verb_noun pattern in snake_case (generate_*, validate_*, review_*). The actions are clear and predictable, making it easy to understand what each tool does.
With 8 tools, the server is well-scoped for its apparent purpose of generating and validating dyslexia-friendly, trauma-informed educational content. Each tool addresses a specific aspect of the workflow, and none feels redundant or unnecessary.
The tool surface covers generation, validation, and review for the core domain, but lacks tools for updating or managing existing activities/content. However, for a generator-focused server, the missing pieces are minor and can be worked around externally.