XR875 Build MCP
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_m33B | Build the M33 core (lunch_rtos 35 && m clean && m). |
| build_otaC | Build the M33 OTA (lunch_rtos 35 && ota_mrtos clean && ota_mrtos). |
| build_c906C | Build the C906 core (lunch_rtos 34 && m clean && m). |
| build_allB | Build everything in sequence (M33 -> OTA -> C906 -> Pack). |
| pack_firmwareB | Pack the firmware (lunch_rtos 34 && pack). |
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 5 tools
Each tool has a clearly distinct purpose targeting specific build components or stages: build_all for sequential builds, build_c906 for C906 core, build_m33 for M33 core, build_ota for M33 OTA, and pack_firmware for packing. No ambiguity exists as each tool name directly corresponds to a unique build operation.
All tools follow a consistent verb_noun pattern with 'build_' or 'pack_' prefixes and specific suffixes (e.g., build_all, build_c906, pack_firmware). This predictable naming scheme makes it easy to understand each tool's function at a glance.
With 5 tools, this server is well-scoped for its build automation purpose. Each tool serves a distinct and necessary function in the build process, from individual component builds to sequential builds and packing, with no redundant or missing operations.
The tool set provides complete coverage for the build domain: it includes individual builds for all core components (M33, C906, OTA), a sequential build tool (build_all), and a packing tool (pack_firmware). This covers the entire build lifecycle from compilation to packaging with no obvious gaps.