Frame Pulse MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELEGRAM_CHAT_ID | No | Telegram chat ID for notifications | |
| TELEGRAM_BOT_TOKEN | No | Telegram bot token for notifications |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_system_healthA | Check if workstation is safe for heavy creative workloads. |
| scan_creative_appsC | Find active creative applications (Blender, Unreal, Maya, etc.). |
| throttle_processA | Reduce CPU priority of a process to prevent overheating. ALIASES: Also responds to "deprioritize" for clarity. Args: target_pid: Process ID to throttle. If None, auto-throttles highest CPU consumer. Returns: Confirmation message with explanation of what was done. |
| deprioritize_processA | SAME AS THROTTLE — reduces CPU priority of a process. Use this if "throttle" sounds too aggressive. Same function, clearer language. Args: target_pid: Process ID to deprioritize. If None, auto-selects highest CPU consumer. Returns: Confirmation with full explanation of effects. |
| emergency_throttle_processA | EMERGENCY: Immediately reduce priority without confirmation. Use when:
Returns: Action taken, minimal explanation. |
| restore_priorityA | Restore a throttled process to normal CPU priority. Use this to 'undo' a throttle/deprioritize if you throttled the wrong process or if your main render finished and you want full performance back. Args: target_pid: Process ID to restore to normal priority (REQUIRED, no auto-detect for safety) Returns: Confirmation of priority restoration. |
| prioritize_processA | Give a process HIGHER than normal CPU priority. WARNING: Use sparingly. High priority can make system unresponsive. Use only when:
Args: target_pid: Process ID to boost (REQUIRED) Returns: Confirmation with warning about side effects. |
| get_thermal_status_aliasD | Alias for check_system_health. |
| find_render_processes_aliasC | Alias for scan_creative_apps. |
| emergency_throttle_aliasD | Alias for throttle_process. |
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 10 tools
Multiple tools are aliases or near-duplicates (e.g., throttle_process, deprioritize_process, emergency_throttle_alias, emergency_throttle_process), making it hard for an agent to distinguish between them without careful reading. Similarly, find_render_processes_alias duplicates scan_creative_apps, and get_thermal_status_alias duplicates check_system_health.
Tool names use a mix of verbs like check, deprioritize, emergency_throttle, find, get, prioritize, restore, scan, throttle with no consistent pattern. The inclusion of '_alias' suffixes alongside action-oriented names adds inconsistency.
The total of 10 tools is within the normal range, but nearly half are redundant aliases, making the set feel bloated. The actual distinct functionality is only 5 operations, suggesting the tool count could be streamlined.
Core operations for CPU priority management are covered (health check, app scanning, throttle/deprioritize, emergency throttle, restore, boost). However, missing generic process listing and ability to set arbitrary priority values are minor gaps that could affect some workflows.