archviz_mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONUTF8 | No | Set to 1 to ensure UTF-8 mode; shown as an environment variable in the example MCP client configuration. | 1 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| reference_sourcesA | Report supported live sources and storage behavior; does not fetch or crawl. |
| search_referencesA | Search OfficeNext live by 1-4 Russian keywords or project name. Returns candidate project links, not verified design matches. Break complex briefs into several short queries. No database/index. |
| read_referenceA | Read a live OfficeNext project: authors, stated dates/materials, relevant text excerpts and all gallery image URLs. focus selects excerpts by keyword. Does not download images or infer visuals. |
| view_reference_imageA | View ONE gallery photo from a verified OfficeNext project in memory, without a local image file. Use indices returned by read_reference. Image is max 1600px for visual review. Preserve attribution. Viewing a photograph does not establish hidden construction, dimensions, cost or acoustic performance. |
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 role: reporting sources, searching candidates, reading project details, and viewing a single gallery image. The search/read/view split is clear, and descriptions explicitly state boundaries such as search returning candidates versus read returning verified project content.
Three tools follow a clear verb_noun pattern: search_references, read_reference, view_reference_image. reference_sources is a noun phrase rather than an action, but it is still readable and semantically appropriate as a metadata/reporting tool.
Four tools are well scoped for a focused workflow around searching, reading, and visually inspecting OfficeNext references. It is slightly thin but each tool earns its place without unnecessary overlap.
The surface covers source discovery, keyword search, project reading, and image viewing, which is a coherent lifecycle for the stated reference-inspection purpose. Minor gaps include no browse/list operation independent of search and no batch image viewing, but these are workable limitations.