Taiwan Building Code Tracker
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 | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_building_codeA | Search for official law articles in the 'Taiwan Building Code - Construction Works' (建築技術規則建築構造編). [IMPORTANT] The search 'query' MUST be in Traditional Chinese. Extract 1-3 core nouns from the conversation (e.g., '活載重', '地震力', '基礎構造') and use them as the query. Do not use long sentences. |
| search_building_interpretations | Search for official interpretations (解釋函) and administrative orders (解釋令) from the Taiwan National Land Management Agency (內政部國土管理署). [IMPORTANT] Use this tool whenever the user mentions '解釋函' or '解釋令'. The search 'query' MUST be in Traditional Chinese (e.g., '採光', '違章建築', '防火避難'). Use 1-2 core nouns from the conversation. This tool returns document numbers and official URLs; you MUST provide these URLs to the user for verification. |
| refresh_dataA | Forcefully re-fetch the latest law articles from the official database and update the local cache. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-building-case | 綜合案例適法性分析 (Comprehensive Case Analysis) |
| track-interpretations | 解釋函令深度追蹤 (Interpretation Deep Dive) |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one updates the local cache, the other searches the building code content. There is no ambiguity or overlap between them.
Both tools follow the same verb_noun pattern: refresh_data and search_building_code. This is consistent and predictable.
Two tools is a minimal but defensible set for a narrow tracker purpose. It feels slightly thin, but each tool serves a clear need: keeping data current and searching it.
The server covers the core search and data-refresh workflow, but lacks additional useful operations such as listing article categories, fetching a specific article by number, or showing version history. Agents can work around this for basic queries, but some natural lookups are missing.