Canadian Building Code 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_codesB | List all available Canadian building codes |
| search_codeC | Search building code sections by keywords |
| get_sectionC | Get details of a specific section |
| get_hierarchyC | Get parent, children, siblings of a section |
| set_pdf_pathC | Connect your PDF for text extraction (BYOD) |
| verify_sectionB | Verify if a section exists and get its formal citation (use this to prevent hallucination) |
| get_applicable_codeB | Get which building codes apply to a Canadian location (city, province, or territory) |
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 7 tools
Each tool has a clearly distinct purpose with no overlap: get_applicable_code determines location-based applicability, get_hierarchy navigates section relationships, get_section retrieves section details, list_codes enumerates available codes, search_code performs keyword searches, set_pdf_path handles PDF integration, and verify_section validates section existence. The descriptions make it unambiguous which tool to use for each task.
All tool names follow a consistent verb_noun pattern with snake_case: get_applicable_code, get_hierarchy, get_section, list_codes, search_code, set_pdf_path, and verify_section. The verbs (get, list, search, set, verify) are appropriately chosen for their actions, and the nouns clearly indicate the target resources, creating a predictable and readable naming scheme.
With 7 tools, this server is well-scoped for its purpose of accessing and navigating Canadian building codes. The count is sufficient to cover core operations like listing, searching, retrieving details, verifying sections, managing hierarchies, handling location applicability, and integrating PDFs, without being overwhelming or sparse. Each tool earns its place in the workflow.
The toolset provides strong coverage for the domain of building code access and navigation, including listing codes, searching, retrieving section details, verifying existence, and handling hierarchies and location applicability. A minor gap is the lack of update or modification tools, but this is reasonable for a read-only reference server, and the PDF integration via set_pdf_path adds flexibility for text extraction.