Construction 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 |
|---|---|
| calculate_materialsC | Calculate construction materials needed for basic structures |
| estimate_costC | Quick cost estimation for materials |
| read_group_messagesA | Read recent messages from WhatsApp group |
| send_group_messageB | Send a message to WhatsApp group |
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 4 tools
Each tool has a distinct purpose: calculate_materials and estimate_cost are clearly separate construction functions, while read_group_messages and send_group_message are distinct messaging operations. There is no overlap or ambiguity between any of the four tools.
All tool names follow a consistent snake_case verb_noun pattern (calculate_materials, estimate_cost, read_group_messages, send_group_message). The naming is uniform and predictable.
Four tools is within the typical well-scoped range, but the mix of construction and messaging tools suggests a lack of focus. The count itself is reasonable, though the server's purpose is diluted across two unrelated domains.
For a construction server, the surface is severely incomplete—only material calculation and cost estimation are covered, with no project management, scheduling, or lifecycle operations. The messaging tools are unrelated and appear bolted on, leaving the overall domain coverage fragmented.