Domera MCP Server
OfficialServer 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| swedish_building_obligationsA | Lists the inspections a Swedish apartment building or commercial property must or should have (OVK ventilation check, energy declaration, lift inspection, radon, legionella, fire safety), with interval, legal basis, who may perform it and, when last-done dates are given, whether each is done, due soon or overdue. Free, no account. General information, not legal advice. |
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 1 tool
With only a single tool there is no possibility of misselection between tools; the purpose (list Swedish building inspection obligations with intervals, legal basis, and status) is unambiguous. An agent will always know when to call it.
The single name is snake_case and descriptive, following a noun-oriented convention rather than a verb_noun pattern. Consistency cannot really be assessed with one tool, but the name is readable and domain-specific.
One tool is thin for a server that also computes status from last-done dates and covers many inspection types; a detail lookup or per-inspection query would round it out. It is borderline rather than wrong, since the domain is narrow.
The tool covers the core ask (obligations, intervals, legal basis, performer, status), but there is no way to fetch details for a single obligation, list obligations by property type explicitly, or get guidance beyond a flat list. Usable for a first pass, with notable gaps for deeper workflows.