Dongbang Interior · 동방인테리어

실제 시공 사례 찾기

search_construction_cases

Read-onlyIdempotent

Find verified Dongbang Interior (동방인테리어) construction cases from public Soomgo customer reviews. To read a specific reference, pass its exact public id from search results, caseReferences or a canonical ABIS case URL. Otherwise filter by service, building type or a Korean keyword such as 중문, 욕실, 구축, 타일. Returns the review month, work items, customer highlights, a short excerpt and the canonical case page URL. Cite only the case returned. An unknown id yields no match. The tool returns public records and links.

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": "search_construction_cases"
  }
}

Input Schema

Name	Required	Description
`id`	No	Exact public case ID returned by case search or answer references.
`limit`	No
`query`	No	Korean keyword such as 중문, 욕실, 도배, 구축, 타일.
`service`	No	apartment, villa, house, bathroom, entrance (중문·신발장·가벽) or finishing (도배·장판·타일).
`building`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

addedInput schema / properties / id

Added value: +{
+  "description": "Exact public case ID returned by case search or answer references.",
+  "pattern": "^[0-9]{1,16}$",
+  "type": "string"
+}

AddedOct 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the bar is lower. The description still adds meaningful behavior: an unknown id yields no match rather than an error, and results are public records with canonical links that must be cited as returned. It does not discuss result capping or that limit caps at 10, but the safety profile is fully covered.

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 comes first, then the id-vs-filter usage rule, then return shape, then citation guidance — a sensible front-loaded order with no filler sentences. There is minor redundancy between "Returns the review month, work items..." and the closing "The tool returns public records and links."

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 required parameters, no output schema and no annotations beyond the safety hints, the description does the needed work: it explains the two input modes, sketches the response fields, and warns that a miss returns nothing. Only a note on the default/capped result count is missing.

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 coverage is 60%, and the description adds useful semantics for id (accepting an id taken from a canonical ABIS case URL) and for the free-text query (Korean keywords). It says nothing about limit behavior, and building type is only gestured at ("building type") while the schema enum gives no per-value meaning, leaving part of the coverage gap unclosed.

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 description opens with a specific verb and resource: "Find verified Dongbang Interior (동방인테리어) construction cases from public Soomgo customer reviews," which is clearly distinct from the sibling answer/style tools. It also enumerates the return fields (review month, work items, highlights, excerpt, URL). It does not explicitly name the sibling tools it differs from, so it stops short of a 5.

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?

It gives a clear operational fork: pass an exact public id "from search results, caseReferences or a canonical ABIS case URL" to read one reference, otherwise "filter by service, building type or a Korean keyword such as 중문, 욕실, 구축, 타일." That covers both invocation modes well, but no guidance is offered on when to prefer these local case records over the sibling answer-search tools.

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

All Dongbang Interior · 동방인테리어 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?