Skip to main content
Glama

Dongbang Interior · 동방인테리어

인테리어 답변 읽기

get_interior_answer
Read-onlyIdempotent

Read an ABIS public interior answer by the slug returned from search_interior_answers. Returns practical guidance, a checklist and relevant public construction references when available. Photo and floor-plan guides also return a designStart upload action. Call start_interior_design for a tailored visual proposal. Cite the answer for planning guidance and the case URL for the specific work shown. An empty caseReferences list means no case was matched to this topic.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_interior_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

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. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description goes further by disclosing the return shape: guidance, checklist, public construction references, and a conditional designStart upload action for photo/floor-plan guides. It also explains the edge case that an empty caseReferences list means no case matched.

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

Conciseness4/5

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

Purpose and slug source are front-loaded, and each following sentence adds distinct information (return contents, conditional action, sibling routing, citation rule, empty-list semantics). It is dense but not padded, though the citation guidance could be trimmed.

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

Completeness4/5

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

With no output schema, the description carries the burden of explaining returns and does so, including a field-specific edge case and a conditional side-effect action. The main omission is behavior when the slug is invalid or not found.

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

Parameters4/5

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

The single slug parameter has no schema description, but the description compensates by stating the slug is the value returned from search_interior_answers, which tells the agent where to get it. It does not restate the pattern or length constraints, but the schema already enforces those.

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

Purpose5/5

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

States a specific verb and resource ('Read an ABIS public interior answer') plus the exact key needed ('by the slug'), and explicitly ties it to search_interior_answers as the source. This clearly separates it from the search, style, and design-start siblings.

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

Usage Guidelines5/5

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

Names the alternative explicitly: call start_interior_design for a tailored visual proposal, and use search_interior_answers to obtain the slug. It also says when to cite the answer versus the case URL, giving concrete usage conditions rather than leaving routing to inference.

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