CMR Client Health
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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 |
|---|---|
| get_client_healthA | Return a full learning-engagement health snapshot for a single client account, modeled on Content Controller's usage/LearnerHistory report. Includes per-course completion rates, average scores, content freshness (last update date), the client's delivery method (Launcher vs. their own LMS), and contract renewal date. Use this when someone asks how a specific client is doing, wants a health check before a renewal, or needs an overview of a client's engagement. |
| get_lowest_performing_coursesA | Return the lowest-completion courses for a client, sorted ascending by completion rate. Use this to surface renewal risk: low completion means the client isn't getting value from the content, which threatens contract renewal. |
| get_launcher_clientsA | Return all clients delivered via Content Controller Launcher (i.e. clients with NO LMS of their own). For these clients, CMR is the only party with visibility into learner engagement — so proactive monitoring matters most here. Use this to identify which accounts need CMR-side engagement monitoring. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| renewal_health_briefing | Generate a complete pre-renewal health briefing for one client account. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| client_directory | The full roster of client accounts: id, name, delivery method, renewal date, and course count. Read-only reference context for any client-health workflow. |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/RahulModugula/cmr-client-health-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server