Skip to main content
Glama

Dongbang Interior · 동방인테리어

사진으로 AI 시안·제안서 만들기 안내

get_interior_styles
Read-onlyIdempotent

Browse and compare the public ABIS interior style and room catalogs. Also returns the existing optional website preparation guide for compatibility. For creating a personalized visual proposal from the user's photo or floor plan, use start_interior_design.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_interior_styles"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomNoRoom selected by the user; auto when unspecified. Do not guess from a private photo.auto
needsNoAt most three concerns explicitly stated by the user. Catalog IDs only; never send a photo, personal details or a raw conversation.
styleNoStyle explicitly chosen by the user; recommended when unspecified. A written brief is optional on the website.recommended
sourceNoKnown client: chatgpt, claude, gemini, meta, grok, perplexity, copilot, mistral; mcp when unknown.mcp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changed
    • addedInput schema / properties / needs
      Added value: +{
      +  "default": [],
      +  "description": "At most three concerns explicitly stated by the user. Catalog IDs only; never send a photo, personal details or a raw conversation.",
      +  "items": {
      +    "enum": [
      +      "storage",
      +      "light",
      +      "circulation",
      +      "care",
      +      "retain",
      +      "layout"
      +    ],
      +    "type": "string"
      +  },
      +  "maxItems": 3,
      +  "type": "array"
      +}
    • changedInput schema / properties / source / description
      Previous value: -"Known AI client for the handoff link: chatgpt, claude, gemini, meta; mcp when unknown."New value: +"Known client: chatgpt, claude, gemini, meta, grok, perplexity, copilot, mistral; mcp when unknown."
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "mcp",
      -  "chatgpt",
      -  "claude",
      -  "gemini",
      -  "meta"
      -]New value: +[
      +  "mcp",
      +  "chatgpt",
      +  "claude",
      +  "gemini",
      +  "meta",
      +  "grok",
      +  "perplexity",
      +  "copilot",
      +  "mistral"
      +]
  3. Changed5 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / room
      Added value: +{
      +  "default": "auto",
      +  "description": "Room selected by the user; auto when unspecified. Do not guess from a private photo.",
      +  "enum": [
      +    "auto",
      +    "living",
      +    "kitchen",
      +    "bedroom",
      +    "bathroom"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / source
      Added value: +{
      +  "default": "mcp",
      +  "description": "Known AI client for the handoff link: chatgpt, claude, gemini, meta; mcp when unknown.",
      +  "enum": [
      +    "mcp",
      +    "chatgpt",
      +    "claude",
      +    "gemini",
      +    "meta"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / style
      Added value: +{
      +  "default": "recommended",
      +  "description": "Style explicitly chosen by the user; recommended when unspecified. A written brief is optional on the website.",
      +  "enum": [
      +    "recommended",
      +    "modern",
      +    "natural",
      +    "minimal",
      +    "classic",
      +    "vintage"
      +  ],
      +  "type": "string"
      +}
  4. First observed

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the note that a legacy preparation guide is returned 'for compatibility' — useful but under-explained, with no mention of catalog size, pagination, or return shape. That is modest incremental value beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence and the sibling redirect are front-loaded and earn their place. The middle sentence about the 'existing optional website preparation guide for compatibility' is vague jargon that does not tell the agent anything actionable and dilutes an otherwise tight description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four optional parameters, no output schema, and full annotation coverage, the description needs to explain what comes back — and 'catalogs' plus a compatibility guide only partly does. The Korean title ('photo-based AI proposal guide') also frames the tool differently from the catalog-browsing described here, leaving a reader unsure whether this returns data or guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and three of four parameters are enums with self-documenting values, so the schema carries the semantic load. The description adds nothing about room, needs, style, or source semantics. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb and resource: 'Browse and compare the public ABIS interior style and room catalogs.' It also routes the agent away from the sibling 'start_interior_design' for personalized proposals. The only drag is the vague second sentence about a 'website preparation guide', which muddies what the tool actually returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states the when-not: for a personalized visual proposal from a photo or floor plan, use start_interior_design instead. That is a concrete alternative with a selecting condition. It stops short of covering the other siblings (get_interior_answer, search_interior_answers, search_construction_cases), so it is not a full routing map.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources