Skip to main content
Glama

내만집 (nmjib) — Korean semi-self interior renovation

자재 상품 목록(가격 없음)

nmjib_material_catalog
Read-onlyIdempotent

내만집 스토어에 등록된 인테리어 자재 상품을 카테고리·브랜드·키워드로 찾는다(브랜드·품명·규격만, 가격·재고 수량은 제공하지 않음). 카테고리: 마루/바닥재, 벽 마감, 몰딩, 타일/대리석, 조명, 간접조명, 창호, 블라인드/커튼, 주방 가구, 도어, 현관 수납, 수납장, 제작가구, 욕실, 욕실 옵션, 거울, 실링팬, 손잡이, 도어락/비디오폰, 석재/인조대리석. "내만집에 어떤 강마루 있어?", "제일벽지 실크 벽지 목록" 같은 질문에 쓴다. 가격·구매는 nmjib_material_request(자재 구매·견적 문의) 또는 앱(https://nmjib.com/materials)으로 안내한다.

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

Input Schema

NameRequiredDescriptionDefault
brandNo브랜드명(부분 일치). 예: 동화, 제일벽지, LX
limitNo
queryNo품명·옵션 키워드(부분 일치). 예: 헤링본, 600각, 실크
categoryNo카테고리(한글 또는 키). 예: 마루, 벽지, 타일, 조명, 욕실 옵션

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description adds genuinely new behavioral context: results contain only brand, product name and spec, with price and stock quantity deliberately omitted — an agent cannot learn that from the annotations. It stops short of describing pagination or how the limit interacts with total result count.

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, then the category vocabulary, then example questions, then the hand-off to purchase — a sensible front-loaded order with no filler sentences. The 20-item category list is dense but earns its place because the schema has no enum for those values; only the length of that inline list keeps this from a 5.

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 should indicate what comes back, and it does specify the returned fields (brand, name, spec) and the excluded ones. For a zero-required-parameter read tool with four simple filters, that plus the usage routing covers what an agent needs. Only the absence of any note about result-count limits keeps it at 4.

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?

Schema coverage is 75% and the three filter parameters already carry their own descriptions, but the schema has no enums, so the enumeration of 20 valid categories in the description materially improves the category parameter's usability. The description's mention of partial-match keyword/brand searching reinforces the schema. The limit parameter gets no added meaning, which keeps this below a 5.

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?

The description opens with a specific verb and resource ('내만집 스토어에 등록된 인테리어 자재 상품을 ... 찾는다') and immediately scopes the result to brand/product-name/spec while excluding price and stock quantity. It is clearly distinguishable from nmjib_material_request, which is named as the purchase/quote path, so an agent can pick the right tool without opening a schema.

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?

It gives concrete trigger queries ('내만집에 어떤 강마루 있어?', '제일벽피 실크 벽지 목록') that show exactly the question shape this tool answers. It also states the negative case, routing price and purchase intent to nmjib_material_request or the web app, which is an explicit when-not plus a named alternative.

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.