Roomvana 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_design_stylesA | List the interior-design styles Roomvana can render (e.g. modern, japandi, industrial), each with a short description. Use this to pick a |
| list_room_typesA | List the room and outdoor space types Roomvana can redesign (interior rooms, house exterior, and garden/outdoor spaces). Use this to pick a |
| design_a_roomA | Turn a room + style choice into a Roomvana studio link with those options pre-selected. The user opens the link, uploads a photo of the room, and gets an AI redesign in about 30 seconds. Validates the room and style against Roomvana's live catalog. |
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 3 tools
Each tool targets a distinct, non-overlapping purpose: two lookup helpers for separate dimensions (styles vs. rooms) and one action tool that composes them. There is no realistic way to confuse them, and the descriptions explicitly cross-reference each other to reinforce the intended workflow.
All three tools use a clean snake_case verb_noun pattern: list_design_styles, list_room_types, and design_a_room. The two listing tools are perfectly parallel, and the action tool follows the same verb-first convention.
Three tools is reasonable for a narrowly scoped link-generation flow: two enumeration helpers plus one generator. It sits at the lean end of appropriate, but each tool clearly earns its place with no redundancy.
The surface covers the core flow of discovering valid styles/rooms and producing a pre-configured design link. Minor gaps exist (e.g. no way to check the status or result of a generated design, or fetch account history), but these fall outside the intended handoff where the user completes the workflow externally.